catch(...) and forced unwind

[Richard Henderson]

On Mon, Dec 15, 2003 at 12:20:18AM -0500, David Abrahams wrote:
> > If you don't want to know about pthread_setcancelstate, then you should
> > not use pthread_cancel either.  If you never use pthread_cancel, then
> > none of this thread is even relevant.
> 
> I'm a library provider ;-)

Then you have to either have to document that the library is
not cancelation safe and point users at TFM when they don't
read it, or expect pthread_cancel to be used and thus call
pthread_setcancelstate appropriately.


r~