Re: Uncaught exceptions not terminating my app
Re: Uncaught exceptions not terminating my app
- Subject: Re: Uncaught exceptions not terminating my app
- From: "Paul Sanders" <email@hidden>
- Date: Thu, 28 Jan 2010 19:37:07 -0000
Yes, I think I came across one of those in the Carbon menu stuff
as I reported in my original post. But I don't think that is
relevant. As I say, I silently ignore those very few exceptions
that the frameworks do occasionally throw in the absence of any
error in my own code, and I have formed the distinct impression
that these are only thrown as an oversight.
Or, if you prefer, a bug. I should probably report them. They
seem to be messages sent to types of NSEvent object that do not
understand them.
Paul Sanders.
----- Original Message -----
From: "Jens Alfke" <email@hidden>
To: "Paul Sanders" <email@hidden>
Cc: "Ken Thomases" <email@hidden>;
<email@hidden>
Sent: Thursday, January 28, 2010 6:55 PM
Subject: Re: Uncaught exceptions not terminating my app
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.)
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden