Re: NSScanner Failing with EXC_BAD_ACCESS
Re: NSScanner Failing with EXC_BAD_ACCESS
- Subject: Re: NSScanner Failing with EXC_BAD_ACCESS
- From: Dave Keck <email@hidden>
- Date: Fri, 15 Oct 2010 22:45:57 -0400
> The problem is probably that theScannedString has never been initialize
> it. Always initialize when you declare, because otherwise your value could
> be nonsense and can't be logged. So, minimally, you'd say this:
Good advice regarding initialization, but...
> 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.
_______________________________________________
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