[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: strange NSException code
From: |
Richard Frith-Macdonald |
Subject: |
Re: strange NSException code |
Date: |
Thu, 1 Dec 2005 18:26:09 +0000 |
On 30 Nov 2005, at 05:15, Lloyd Dupont wrote:
Why is it that the default exception code call exit()
Because that causes the program to terminate cleanly .
Because it's what the spec/compatibility dictates.
Because there seems no other reasonable behavior.
why not let the program crahs normally?
Why do you want the program to crash? and how are you going to make
it 'crash normally'? if the handler did not terminate the program,
the program would try to continue ... and could do anything ...
corrupt data/files, bill your customers for things you didn't deliver
them etc. Often it might crash pretty immediately, occasionally it
might continue to work with a minor glitch ... but most people
wouldn't want that sort of unpredictable behavior.
at least that would gives more information!
I don't believe so.
- strange NSException code, Lloyd Dupont, 2005/12/01
- Re: strange NSException code,
Richard Frith-Macdonald <=
- Re: strange NSException code, Helge Hess, 2005/12/01
- Re: strange NSException code, Andrew Ruder, 2005/12/01
- Re: strange NSException code, David Ayers, 2005/12/02
- Re: strange NSException code, Richard Frith-Macdonald, 2005/12/02
- Re: strange NSException code, David Ayers, 2005/12/02
- Re: strange NSException code, Lloyd Dupont, 2005/12/04
- Re: strange NSException code, Helge Hess, 2005/12/02
- Re: strange NSException code, Adrian Robert, 2005/12/02
- Re: strange NSException code, David Ayers, 2005/12/02
- Re: strange NSException code, Helge Hess, 2005/12/02