Re: Data, enumerateBytes: separate blocks?
Re: Data, enumerateBytes: separate blocks?
- Subject: Re: Data, enumerateBytes: separate blocks?
- From: Daryle Walker <email@hidden>
- Date: Tue, 19 Dec 2017 17:57:42 -0500
> On Nov 28, 2017, at 3:54 PM, Quincey Morris
> <email@hidden> wrote:
>
> I believe that there is one more little piece to this that’s more recent.
> Since (after that 10.9 change) the NSData class had to become (publicly)
> aware that subclasses might contain discontiguous data, the opportunity arose
> for Cocoa to leverage this in other scenarios, where dispatch_data_t (aka
> DispatchData in Swift) wasn’t involved. That’s good in general, as a
> performance enhancement for code that cares to enumerate the block ranges,
> but it happens behind the scenes.
>
> By contrast, AFAIK the only mechanism for 3rd party code to *forcibly* create
> NSData objects with discontiguous data buffers is via
> dispatch_data_t/DispatchData. For that reason, it might make more sense for
> Daryle to work in the DispatchData domain rather than the plain Data domain.
> However, as you say, there’s a bridge involving some simple hoops available
> if necessary.
What are the hoops/bridges required?
—
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT com
_______________________________________________
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