Re: What risk of undefined behavior if destructor must throw?

Terry G wrote:


< snip example >

Basically:

- Do not throw any exceptions from your own destructors.
- If your destructors are calling methods that may cause an exception
to be thrown, be certain to catch them and eat them so they don't leak
from the destructor. It is ok if an exception is thrown during the
destructor's call as long as it is caught, i.e. it does not leak out of
the destructor.

The most basic thing you can do in a destructor is

Foo::~Foo
{
   try
   {
      // do what you need to do
   }
   catch ( ... )
   {
   }
}

You may wish to attempt to log an error thus:

Foo::~Foo
{
    try
    {
     // do stuff
    }
    catch ( const std::exception & x )
    {
        do_log( x.what() );
    }
    catch ( ... )
    {
   }
}

Of course you must be certain here that do_log doesn't throw. If it
might then put another try..catch round it. If you're doing this a lot
of course you'll write non-throwing adapters.

--
      [ See http://www.gotw.ca/resources/clcm.htm for info about ]
      [ comp.lang.c++.moderated. First time posters: Do this! ]