From: Slawomir Lisznianski (slisznianski_at_[hidden])
Date: 2005-08-26 09:42:52
On Fri, 26 Aug 2005 09:18:25 -0400, "David Abrahams"
> What's expected doesn't matter. It's what's implemented that counts.
I think, in the context of this discussion, it matters quite a lot. What
we are debating specifically, is whether a library can allow for
customization, yet leave an option of having a default (usually commonly
expected) behavior of coring with a full stack trace.
The alternative to that, as you pointed out, is to log a message and
then abort, or eat the exception, which can easily be done by the user,
by her wrapping the `thread' function with the catch-all one.
To preserve the compatibility, the thread_proxy could install an
exception handler which doesn't call abort().
-- Slawomir Lisznianski
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk