Re: odd behavior with NSError?
Re: odd behavior with NSError?
- Subject: Re: odd behavior with NSError?
- From: Greg Guerin <email@hidden>
- Date: Thu, 15 Oct 2009 23:31:16 -0700
Bill Bumgarner wrote:
On Oct 15, 2009, at 10:41 PM, Nathan Vander Wilt wrote:
...
You're saying that some methods go out of their way to trample my
(potentially unavailable) error storage even on success?
If the error storage is not available, as indicated by passing an
NSError** of nil, then the unavailable error storage is never
written. Correct?
I just want to be sure I understand this completely.
-- GG
_______________________________________________
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