Re: Proper Destruction of Class Members when an Exception is Thrown in Destructor

From:

anon <sfddfgd@ebay.de>

Newsgroups:

comp.lang.c++

Date:

Fri, 27 Feb 2009 17:46:26 +0100

Message-ID:

<go95d2$rk9$1@news01.versatel.de>

AnonMail2005@gmail.com wrote:

Of course it's relevant because it answered my specific question.

*******
15.2.2 says:
An object that is partially constructed or partially destroyed will
have destructors executed for all of its fully constructed subobjects,
that is, for subobjects for which the constructor has completed
execution and the destructor has not yet begun execution. Should a
constructor for an element of an automatic array throw an exception,
only the constructed elements of that array will be destroyed. If the
object or array was allocated in a new-expression, the matching
deallocation function (3.7.3.2, 5.3.4, 12.5), if any, is called to
free the storage occupied by the object.
******

For an exception thrown from a destructor ***during stack
unwinding***, the *default* action is to terminate the process. So
that only happens during stack unwinding - i.e. when an exception has
already been thrown.

Sorry I misunderstood you.

The answer to your question is : yes, all constructed class members will
be properly destructed.

And unless you are doing something like in the following example, your
process should be properly destructed as well :P

struct A
{
   ~A() { throw "hi"; }
};

int main()
{
  try
  {
     A *a = new A;
     try
     {
      delete(a);
     }
     catch(...)
     {
     }
  }
  catch(...)
  {
  }
}