On Mon, Nov 2, 2009 at 10:06 PM, Roland King <r...@rols.org> wrote: > Haven't there been several threads recently telling people *never* to use > the if( saveError ) check because saveError may be set even if the method > succeeds.
You can use it to determine if there is an error object available. If the method returns NO, it better return a valid NSError or set the pointer to nil. --Kyle Sluder _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
