On Jan 28, 2010, at 9:53 AM, Paul Sanders wrote:
No more dangerous then doing a random longjmp back to the event loop, which is what happens if you let the exception unwind. As I say, the frameworks do not appear to use exception handling internally, other than to get back to the event loop in this way.
There are various places in the frameworks where exceptions get caught and (mostly) ignored. Some of these are where Carbon code (like the menu or open/save file panel implementation) calls into Cocoa, since throwing an exception out through Carbon is bad news.
(The Carbon examples may not be true anymore in 10.6, but they are in 10.5 and earlier.)
—Jens _______________________________________________ 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
