Re: odd behavior with NSError?
Re: odd behavior with NSError?
- Subject: Re: odd behavior with NSError?
- From: Colin Howarth <email@hidden>
- Date: Fri, 2 Oct 2009 22:18:07 +0200
On 2 Oct, 2009, at 07:36, 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];
The way you pass "enc" is also wrong. If the method had actually
succeeded, your program would have crashed.
NSStringEncoding enc;
NSError *error;
NSString *file = [NSString
stringWithContentsOfFile:@"/Users/colin/developer/Trace/glass.csv"
usedEncoding:&enc error:&error];
Thanks, I thought it looked odd.
But, hmmph! I'm used to everything being an object. If it had simply
been
+ (id)stringWithContentsOfFile:(NSString *)path encoding:(int *)enc
error:(NSError **)error
I'd have been alright :-)
--colin
_______________________________________________
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