Re: EXC_BAD_ACCESS in NSData
Re: EXC_BAD_ACCESS in NSData
- Subject: Re: EXC_BAD_ACCESS in NSData
- From: Pax <email@hidden>
- Date: Mon, 26 May 2014 17:06:44 +0100
Shameful. I need more sleep! :-) I also need to reread my code more carefully before asking questions.
As I say though, I think that the solution I posted is the better solution anyway - since who wants a copy, with the additional overhead that a copy entails, when you don't need to have one?
On 26 May 2014, at 16:33, Roland King <email@hidden> wrote:
> Too true. That was a lot of bugs in 4 lines!
>
>> On 26 May, 2014, at 11:18 pm, Scott Ribe <email@hidden> wrote:
>>
>>> On May 26, 2014, at 9:05 AM, Roland King <email@hidden> wrote:
>>>
>>> The first one of those is ok...
>>
>> No, it's not--take a closer look ;-)
>>
>>> unsigned char* databuffer = (unsigned char*)malloc(datasize);
>>> [datastream getBytes:&databuffer range:NSMakeRange(positionCounter, datasize)];
>>
>>
>> --
>> Scott Ribe
>> email@hidden
>> http://www.elevated-dev.com/
>> (303) 722-0567 voice
>>
>>
>>
>>
_______________________________________________
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