Dave Butenhof wrote: [...] > Indeed. The only real (and unfortunately the hardest) questions are how > to reconcile the (apparent) contradictions between cancel scope and C++ > throw specs (explicit or implicit as in destructors), Fix ES (get rid of ugly implicit catch(...) semantics and totally idiotic transfer of terminate()/unexpected() handlers up-stack along with unexpected exception), mandate 2-phase EH and intelligent cancel delivery. http://groups.google.de/group/comp.lang.c++.moderated/msg/c897f898de7a97cd > and cultural > investment in catch(...). Invest in weak_catch(). > > Perhaps integration would be simplified if threads created using native > C++ mechanisms (rather than the C pthread_create) started with > cancellation disabled, allowing C++ programs to enable where desired. That would go against the premise of POSIX's modulary argument http://www.codesourcery.com/archives/c++-pthreads/msg00419.html and would not really solve any problems. http://www.codesourcery.com/archives/c++-pthreads/msg00425.html http://www.codesourcery.com/archives/c++-pthreads/msg00445.html regards, alexander.