|
Boost : |
From: Hillel Y. Sims (hsims_at_[hidden])
Date: 2002-10-04 12:37:46
"Victor A. Wagner, Jr." <vawjr_at_[hidden]> wrote in message
news:4.3.1.2.20021004091541.042075b0_at_mail.rudbek.com...
> >
> >unless the entire thread running vector2.push_back(e2) gets >>canceled<<
> >hitting some cancellation point or async-cancel region... on "some"
> >C/*C++* implementation that DOESN'T invoke catch(...) handlers on thread
> >cancellation (or exit)... and this IS "industry practice" (AIX, Solaris,
> >pthreads-win32/non-VCE, probably z/OS, etc.), nowadays, BTW. ;-) ;-)
>
> which, of course, means you can never do exception safe things in such an
os
>
>
It means that use of catch(...) is not 100% safe in such an OS.
"Hillel Y. Sims" <hsims_at_[hidden]> wrote in message
news:an9ttm$bf0$1_at_main.gmane.org...
>
> - ScopeGuard
>
> - CancelGuard - disable thread-cancellation in critical regions
> (platform-specific implementation: no effect on non-pthread platforms)
>
> - NoThrowGuard - similar protection as "throw()" spec, but can be applied
at
> any block scope without need for interface-polluting ES, also provides
> cancellation protection via CancelGuard. (
> http://groups.google.com/groups?&th=e8754b0adf00544 )
>
:-)
hys
-- Hillel Y. Sims FactSet Research Systems hsims AT factset.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk