On Jun 23, 2012, at 10:46 PM, Roland King wrote: > Yes that is a general statement. You should check the return value of the > method and only if it indicates there's an error, check the error object. > There is no guarantee that the error object was not set at some point during > the method processing, even if that method eventually succeeds, nor that it's > forced clear on success.
What if you explicitly set your NSError variable's value to nil immediately before using it? Wouldn't it be safe to trust in that case? _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
