Re: NSScanner Failing with EXC_BAD_ACCESS
Re: NSScanner Failing with EXC_BAD_ACCESS
- Subject: Re: NSScanner Failing with EXC_BAD_ACCESS
- From: Matt Neuburg <email@hidden>
- Date: Sat, 16 Oct 2010 19:57:42 -0700
- Thread-topic: NSScanner Failing with EXC_BAD_ACCESS
On Fri, 15 Oct 2010 22:45:57 -0400, Dave Keck <email@hidden> said:
>>
>> NSString *theScannedString = nil;
>>
>> Now you can log that value successfully, even if nothing gets written
>>into
>> it. Then you can track down *why* nothing is getting written into it.
>>:) m.
>
>No initializing theScannedString doesn't excuse you from checking
>the return value of -scanCharactersFromSet:. See Bill's response.
Point taken! (And not the first time he's made this clear, either.) m.
--
matt neuburg, phd = email@hidden, <http://www.apeth.net/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.apeth.net/matt/default.html#applescriptthings
_______________________________________________
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