Re: [boost] [Boost.Thread]: consider removing catch(...) from thread_proxy

From: Ariel Badichi (abadichi_at_[hidden])
Date: 2005-08-24 22:17:57

Slawomir Lisznianski wrote:
> On Thu, 25 Aug 2005 02:12:12 +0200, "Ariel Badichi"
> 
>>A good solution is to provide a customization point: call a handler that
>>can be replaced by the user.
> 
> 
> The language already provides this customization through set_unexpected
> and set_terminate. 
> 

But terminate/unexpected functions have special semantics that don't
quite fit here. For example, the handler should be able to return.

> Althought no standard mandates it, it is commonly expected that each
> thread can set its own terminate() or unexpected() function -- calling
> set_terminate() or set_unexpected() in one thread affects only the
> exceptions in that thread.
> 
> Cheers,
> 
> Slawomir

Ariel.