[c++-pthreads] Re: C++ and POSIX Threads Mailing List

[Alexander Terekhov]

Schwarz Konrad wrote:
[...]
> Pthread code that is aysnc-cancelation safe needs to take extra 
> precautions (pushing and popping cancelation handlers). ....

Async-cancel-safety enforced by the language will surely help to 
dispose all those myths about "terrible async-cancel". But nobody
was really talking about ASYNC cancel (unless I've just missed 
something). Thus far, the topic is/was synchronous ("deferred")
cancel. Forced unwinding is brain-damaged. And it's absolutely 
not needed (neither for "foreign exceptions" nor jumps). 

http://google.com/groups?selm=3F78478A.F0CCBD0%40web.de

What's really needed is standard mandated (mandatory) 2-phase EH
and some patching of exception specifications (get rid of silly
unwinding on ES violations) plus, perhaps, some extras like weak 
"ATTACHED"[1] cleanup handlers ala "action_on_propagation_of"

http://google.com/groups?threadm=3EBA6888.D4DF2AB1%40web.de

and a few other goodies. ;-)

regards,
alexander.

[1] http://google.com/groups?selm=3eb91018%40usenet01.boi.hp.com