Re: nptl 0.38
"Alexander Terekhov" <[email protected]>
| Newsgroups | gmane.comp.lib.phil |
|---|---|
| Organization | http://freemail.web.de/ |
| Message-ID | <[email protected]> |
Ulrich Drepper <[email protected]> schrieb am 12.05.03 18:53:43: [...] > ~ update of the unwinding code to support the compromise wrt C++ > exception handling. catch(...) blocks are also executed in case > a thread is canceled. Only catch(...), no other catch variant. > This is only logical since the cancellation has no type representable > in C++. Says who? Braindamaged "forced unwinding"-based (for thread cancel and thread exit, jmps aside for a moment) ABI? http://groups.google.com/groups?selm=3D205A8A.DEFC922A%40web.de (Subject: Re: Some issues with Technical Report on C++ Performance (DRAFT)) > Note that the catch(...) block has to rethrow the exception; > otherwise the program will abort. That's crappy too. http://groups.google.com/groups?selm=rJNa8.12%24YS1.142%40news.cpqcorp.net (Subject: Re: PTHREADS: Longjmp()'ing from cleanup handlers) <quote> Sorry, but if you want to "finalize" (catch and continue) a cancellation, you need a correct and rational implementation of POSIX threads that implements cancellation as an EXCEPTION that can be caught. (E.g., with a C++ 'catch(...)', though having a standard name for the exception would be even better.) </quote> http://groups.google.com/groups?threadm=3EC12FB0.1AEAF69A%40web.de (Subject: Re: __attribute__((cleanup(function)) versus try/finally) http://groups.google.com/groups?selm=3EC0ECAA.6520B266%40web.de (Subject: Exception handling... it's time to fix the standard) regards, alexander. ________________________________________________________________ Mit der Grupppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179