Re: Weird controlled behavior - Gnat 3.15p NT

[Hyman Rosen <hyrosen@mail.com>]

Jean-Pierre Rosen wrote:
> And what happens in C++ when an exception is raised by a destructor,
> for this object and for objects not yet finalized?

It is considerd very bad design in C++ to allow exceptions to escape
from destructors, because of the poor semantic meaning of such a thing.
(While you may fail to construct something and so have no object, when
the compiler says it's time to destroy something, it's gone.)

In any case, should an exception be thrown from a destructor, the code
goes on to call destructors for the remaining completely constructed
subobjects of the throwing object, if any, then for other objects whose
lifetimes are ending due to the scope being exited because of the thrown
exception. Should one of those destructors again throw, the special global
function terminate() is called, and the program ends.

I believe that in similar circumstances, Ada does all the finalizations
and then raises Program_Error, so in both languages, Don't Do That (tm).