This is the mail archive of the
mailing list for the Cygwin project.
Re: Unifying Exception types in setup
- From: Pavel Tsekov <ptsekov at gmx dot net>
- To: Max Bowsher <maxb at ukf dot net>
- Cc: cygwin-apps at cygwin dot com
- Date: Sun, 16 Mar 2003 12:27:33 +0100 (CET)
- Subject: Re: Unifying Exception types in setup
On Sun, 16 Mar 2003, Max Bowsher wrote:
> > 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.
> All exceptions are fatal if they get to the toplevel.
Yep! Maybe I made a wrong example. My point was - no other exception
should reach the toplevel except the the one designated to kill setup
i.e. the one which you will use to replace the exit () calls.
If another exception reaches then it should be treated as a bug.
> Unfortunately, we will require multiple toplevel catch blocks: One in each
> WndProc and thread initiation routine.
Btw I remember that Robert had some concerns about exceptions and
mingw. The info should be in the archives. And I don't know if these
problems still exist.