On Nov 20, 2008, at 10:54 AM, Alexander Spohr wrote:
I’d go for #1. If you have an error in status, throw an exception.
In this case, an exception might actually be OK, given that the library is in isolation.
However, it goes against the design patterns of Cocoa and if the code is ever refactored such that there are Foundation or AppKit frames on the stack over which the exception is thrown, the code may break.
Exceptions for non-programmer error are to be avoided. b.bum _______________________________________________ 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]
