This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Sun, 2003-03-16 at 21:24, Pavel Tsekov wrote: > Just chaging exit() -> throw Exception won't help much. There should be > an exception handler installed who takes care of processing these > exceptions i.e. shutdown setup with a simple message describing the > situation. > > If you going to do this I suggest you to dereive a new class from > exception or Exception, say FatalException. Then install a global handler, > which catches FatalException and displays a message then exits. This way > the exit call will be in a single place and not scattered throught the > code. Yep, thats reasonable. terminate handlers can't return though, so we need a synchronous, non memory allocating, non resource using message display. Rob -- GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.
Attachment:
signature.asc
Description: This is a digitally signed message part
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |