search for: stroustroup

...up another? For instance, if A's destructor also throws an exception? A's exception was not thrown while processing B's exception (but while cleaning up *before* processing it), so it's not a nested exception, but an "aside" exception... It makes my head hurt... I think Stroustroup didn't want to think about that, too... :D cheers, --renato

Hi Renato, >> I don't understand what you are saying. Cleanups (e.g. destructors) > > Hi Duncan, > > Cleanup landing pads normally call destructors, but they're not a > destructor themselves. I'm simply saying that compiler generated > blocks (such as cleanups) should never depend on user variables. I see what you are saying now. Unfortunately optimizations

...ed (at which spot would you throw the exception?). > A's exception was not thrown while processing B's exception (but while > cleaning up *before* processing it), so it's not a nested exception, > but an "aside" exception... > > It makes my head hurt... I think Stroustroup didn't want to think > about that, too... :D Actually it's pretty simple, see above. Ciao, Duncan.

On 25 November 2010 11:03, Duncan Sands <baldrick at free.fr> wrote: > I don't understand what you are saying.  Cleanups (e.g. destructors) Hi Duncan, Cleanup landing pads normally call destructors, but they're not a destructor themselves. I'm simply saying that compiler generated blocks (such as cleanups) should never depend on user variables. But I get what you're