|
Boost : |
From: Peter Dimov (pdimov_at_[hidden])
Date: 2002-08-08 08:42:06
From: "Dale Peakall" <dale.peakall_at_[hidden]>
>
> OK, I can finally see why you might want an exception to escape from your
> thread, and I can see why its "logical" to want this specifically when
> dealing with threads that return values. But as stated above, I prefer
> consistency over "twistic logic".
I don't like inconsistencies. When it comes down to comparing alternative
approaches, this should be taken into account. But consistency is not the
only factor.
> My thread-usage generally involve long-lived threads that are only joined
as
> part of tidy system shutdown and as I've stated I want my application to
> terminate on uncaught exceptions in the thread as they always indicate an
> error.
Note how the inconsistent thread<void> hack "does the right thing" in this
situation, too.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk