EH in egcs

[Oleg Krivosheev]

On Sun, 26 Oct 1997, H.J. Lu wrote:

> > 
> > >>>>> H J Lu <hjl@lucon.org> writes:
> > 
> > > That is nested throw/catch doesn't work. That is because
> > > __eh_value/__eh_type are used throughout EH and the new ones will
> > > override the old ones. I was wondering if we could do this in the catch
> > > region:
> > 
> > > Treat the caught exception as a local variable.
> > 
> > That's not enough.  You can have multiple uncaught exceptions active at
> > once.  We need to build a stack of exceptions.
> > 
> 
> How come there are multiple uncaught exceptions active at the
> same time? I assume we are not talking about multithreading.
> 
> When an exception is thrown and it is not caught, who will
> throw another exception? The only thing I can think of is
> throw () itself, which I don't know should throw any exceptions
> by itself.

exceptions in any destructor called during stack unwinding 
after first one ?

i remember to read thread in c.l.c++.m about this.
The conclusion was that is legal while being
bad style

OK