On 19/07/2012, at 12:55 AM, Alex Zavatone wrote: > But doesn't the other way around, calling an undefined method in/on an > object, instantly SIGABRT?
It throws an exception. How the exception is handled will vary. In an app it usually reaches the top and gets ignored, but sometimes it could end up calling abort(). I've seen a few exceptions deep in Cocoa do that lately (along with a rather helpful message stating that a piece of unreachable code was reached!). --Graham _______________________________________________ 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
