• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Data, enumerateBytes: separate blocks?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Data, enumerateBytes: separate blocks?


  • Subject: Re: Data, enumerateBytes: separate blocks?
  • From: Quincey Morris <email@hidden>
  • Date: Tue, 19 Dec 2017 17:08:54 -0800

On Dec 19, 2017, at 14:57 , Daryle Walker <email@hidden> wrote:
>
> What are the hoops/bridges required?

I think I was referring to what Wim Lewis said, which is that you can create
DispatchData values (or perhaps dispatch_data_t objects), but you’re going to
have to forcibly cast from dispatch_data_t to its superclass, and then bridge
that to Data.

However, if you’re going to the trouble of creating DispatchData values, you
may as well use those directly, rather than bridging across to Data. The
decision may depend on exactly which APIs you need to use to process the data.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Data, enumerateBytes: separate blocks?
      • From: Daryle Walker <email@hidden>
References: 
 >Re: Data, enumerateBytes: separate blocks? (From: Daryle Walker <email@hidden>)

  • Prev by Date: Re: Data, enumerateBytes: separate blocks?
  • Next by Date: Pasteboards and NSSecureCoding
  • Previous by thread: Re: Data, enumerateBytes: separate blocks?
  • Next by thread: Re: Data, enumerateBytes: separate blocks?
  • Index(es):
    • Date
    • Thread