Handling exceptions in a destructor?

[dean]

What's the generally accepted way to handle an exception in a
destructor? We just found out the hard way that throwing an exception
is not going to work.

-Dean

[wittempj]

see http://www.parashift.com/c++-faq-lit....html#faq-17.3

[dean]

Thanks that rounds it up nicely.

Dean

[Ali Çehreli]

"wi******@hotmail.com" <ma**********@gmail.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...

see http://www.parashift.com/c++-faq-lit....html#faq-17.3

Unfortunately the FAQ misses an important point.

It is not "not to throw" but "not to escape" exceptions from destructors. A
guideline from Exceptional C++ by Herb Sutter:

<quote>
Never allow an exception to escape from a destructor or from
an overloaded operator delete() or operator delete[]();
write every destructor and deallocation function as though it
had an exception specification of "throw()."
</quote>

Ali

[Ian]

dean wrote:

What's the generally accepted way to handle an exception in a
destructor? We just found out the hard way that throwing an exception
is not going to work.

Catch them and either ignore them, log something or assert, depending on
where you are in development and your policies.

Ian