On Thu, Mar 20, 2008 at 4:56 AM, Jens Alfke <[EMAIL PROTECTED]> wrote:
> The ...noCopy family of methods are really just suggestions. They > don't guarantee that the Foundation object will use that block of > memory for its internal storage, only that it'll take ownership of the > block and free it when it's done with it. In that case I think they're rather badly named. Particularly given that -[NSMutableData dataWithBytesNoCopy:b length:d freeWhenDone:NO] does not take ownership of the block, i.e., behaves exactly the same as -[NSMutableData dataWithBytes:b length:d] Hamish _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
