Re: Allowing Applications to continue after exception...

[David Ayers]

Am Mittwoch, den 04.02.2009, 23:52 -0500 schrieb Gregory Casamento:
> The attached test program does not crash on Mac OS X when the button
> is pressed, but does crash on GNUstep.  The button calls the "action:"
> method in Controller which immediately throws an exception.
> 
> I believe this confirms that GNUstep's behavior is inconsistent with
> Cocoa.   I can test on OpenStep, but I suspect that the behavior is
> the same there as it is on Cocoa.

FWIW, IIRC this inconsistency was intentional an I believe for a very
good reason.  I thought we had documented it at the time but I can't dig
it up easily right now.

An uncaught exception indicates that the application is in an undefined
state.  For certain type of applications (like viewers) this can be
ignored.  For editor application this could mean that the document being
edited could be corrupted and saving it cause data corruption.

This thread is the only reference I found in which we suggested some
type of "Developer-Mode" which indicates that "I know what I'm doing,
let me debug, will you?!".

http://lists.gnu.org/archive/html/discuss-gnustep/2004-10/msg00092.html

I still believe that handling generic handling of exceptions in the
runloop is a dangerously wrong and an implementation detail that we
shouldn't try to be compatible with.  But others may disagree.

Cheers,
David