|
Boost : |
From: terekhov (terekhov_at_[hidden])
Date: 2002-01-17 09:02:29
--- In boost_at_y..., "Peter Dimov" <pdimov_at_m...> wrote:
[...]
> During stack unwinding, stopping the cancel exception is mandatory,
> otherwise the whole process is going to die. For example a C++
exception may
> be on its way up when someone cancels the thread.
But that is N6, unless I am missing something:
">6) Ensure cancellation points don't throw when uncaught_exception()
>returns true."
> With a sticky cancellation
> (you can't 'uncancel' the thread) the C++ exception will be handled
and then
> the next cancellation point will throw pthread_cancel_e or whatever.
and... will be eaten again by some catch(pthread_cancel_e&) without
throw; ...and again...
Hmm.. To me, the purpose is still not clear!
regards,
alexander.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk