Re: Where's the buffer overrun?
Re: Where's the buffer overrun?
- Subject: Re: Where's the buffer overrun?
- From: Chris Suter <email@hidden>
- Date: Thu, 20 Mar 2008 12:42:11 +1100
On 20/03/2008, at 12:31 PM, Nick Zitzmann wrote:
On Mar 19, 2008, at 6:49 PM, Hamish Allan wrote:
I, for one, am surprised that NSMutableData works this way, given
that
a) the method name specifically requests that no copy is made, and b)
there's no particular reason for it to behave that way unless the
data
is resized.
Thanks again everyone. In case Chris Kane or someone else in charge
of (Core)Foundation at Apple is reading this, I filed bug #5809387
on this issue...
I wouldn't hold out too much hope for getting this fixed. From looking
at the CF sources, it looks like it would be a little tricky solve.
I suspect that it will just end up getting documented as behaving this
way and that's fair enough, I think—it is NSMutableData after all.
- Chris
_______________________________________________
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