On Thu, Jul 16, 2009 at 3:54 PM, Quincey Morris<[email protected]> wrote: > If I've misunderstood your point, it would be helpful to see an example of > how your code might look with the NSError-wrapping code in place.
The point is that convenience is increased if NSError-returning methods follow the childhood rule of "if you have nothing useful to say, don't say it at all." IOW, if you're going to return YES, don't muck with *error. Then we don't have to worry about using different techniques for wrapping error objects at different points of the program's flow. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
