Re: odd behavior with NSError?
Re: odd behavior with NSError?
- Subject: Re: odd behavior with NSError?
- From: Matt Neuburg <email@hidden>
- Date: Fri, 02 Oct 2009 08:46:29 -0700
- Thread-topic: odd behavior with NSError?
On Fri, 02 Oct 2009 07:05:37 -0400, Gregory Weston <email@hidden> said:
>Stephen J. Butler wrote:
>
>> On Thu, Oct 1, 2009 at 10:31 PM, Colin Howarth <email@hidden>
>> wrote:
>>> NSStringEncoding *enc;
>>> NSError *error;
>>>
>>> NSString *file = [NSString
>>> stringWithContentsOfFile:@"/Users/colin/developer/Trace/glass.csv"
>>> usedEncoding:enc error:&error];
>While we're at it, the values of enc and error are (effectively)
>nondeterministic before the message send. The documentation for the
>method you're invoking doesn't specify what it'll put into the
>encoding argument on failure or into the error argument on success,
>which means you really shouldn't be blindly using either of them after
>the call. It would be a good idea to get into the habit of
>initializing your local variables at the point of declaration.
And IIRC the Build and Analyze mechanism (clang?) will warn of this. Try it,
you'll like it! m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/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