|
Boost : |
From: Stefan Seefeld (seefeld_at_[hidden])
Date: 2007-03-26 16:13:51
Roland Schwarz wrote:
> Howard Hinnant wrote:
>> 1. Owner to t: I'm no longer interested in your computation (but
>> somebody else might be).
>> 2. Owner to t: I want you to clean-up and stop as soon as possible.
>
> Aren't we trying to ask for too much?
>
> If we were able to
>
> thread t();
> ...
> t.raise(exception);
>
> throw an exception at a thread, the thread itself can take whatever
> action is sensible at this point.
Not sure what "to throw at" means in the context of C++ exceptions.
(I'm afraid we are deviating from the original topic, though.)
With exception-throwing comes stack-unwinding, so the thrower
has to be on top of the call stack, not someone outside (or even
in another thread).
The point really is that we want a means to interrupt an otherwise
non-interruptible (i.e. blocking) call, so this requires support
from the system layer.
Regards,
Stefan
-- ...ich hab' noch einen Koffer in Berlin...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk