20 Feb
2015
20 Feb
'15
3:25 p.m.
Stephen R. van den Berg wrote:
Arne Goedeke wrote:
What kinds of things can safely be done from within destroy() and should we document them?
Well, I for one, "discovered" that *if* any code in destroy() can throw an exception, you must explicitly catch it, because if you don't the exception will be raised and (sometimes/always?) silently discarded.
Strange; do you have a test case? When I read the code it looks like any exceptions will be caught and sent to master()->handle_error().