From: Eric Woodruff (Eric.Woodruff_at_[hidden])
Date: 2002-08-27 01:49:18
Yes, thread exceptions are being discussed. Once the user's functor exits
(via return or thowing an exception), the thread is effectively terminated.
What happens beyond that is based on the chosen policy or implementation
defined besides the fact that the thread<> is now joinable (giving a
possible return value and/or exception).
There is little to discuss about terminate (). The state of the thread
resources is the responsibility of the implementor (William Kempf?).
----- Original Message -----
From: Darryl Green
Sent: Tuesday, 2002:August:27 1:39
Subject: RE: Re: Re: Boost.threads: interthread exceptionconveyance
> From: Eric Woodruff [mailto:Eric.Woodruff_at_[hidden]]
> What is the purpose of that "handler"?
To ensure that the stack *is* unwound and the thread terminates (but not, or
not always, the process).
> When would it do its handling?
When there is an uncaught exception in a thread - that was what was being
discussed (I thought)?
> The purpose of an exception is to terminate with stack unwinding and a
meaningful object that represents why.
Terminate what? An operation that encounters an error - yes.
> Are you looking for a non-exception based alternative to kill
> a thread with?
Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk