Re: [c++-pthreads] Re: Does the cancelation exception have a name?

[Dave Butenhof <david.butenhof@xxxxxx>]

Alexander Terekhov wrote:
> Peter Dimov wrote:
>   
> > Alexander Terekhov wrote:
> >     
> > > Google pthread_exit_e.
> > >       
> > I know about DEC pthread_exit_e, my question was more about g++/glibc/NPTL's
> > implementation and how the people involved feel. DEC's exception doesn't
> > have a C++ name, by the way, 
> >     
> http://groups.google.com/group/comp.programming.threads/msg/271124f3a0517204
>
> "C++ doesn't have a name for those "foreign" exceptions. (Of course 
> destructors work fine.) We've worked with the compiler group to add 
> some builtin exception subclasses to deal with that, but we never 
> found the time to finish hooking up all the bits."
>   
Alexander; perhaps the most telling part of the article you quote here 
is that I wrote it 6 years ago tomorrow; and we still don't have a 
standard for integration of threads and C++, and with Tru64 UNIX reduced 
to irrelevance I don't think there's any current commercial UNIX that's 
even tried to do it right. I feel like everything that can be said has 
circulated more than just a few times before, with little effect. Kinda 
frustrating, really.
> D. 
>
>    std::thread_termination_request (base for cancel and exit)
>    std::thread_cancel_exception
>    std::thread_exit_exception<T>
>    std::thread_longjmp_exception
>   
Yes, absolutely; the parenthesized bit being the most important part... 
a common base class for cancel and exit.
begin:vcard
fn:Dave Butenhof
n:Butenhof;Dave
org:Hewlett-Packard Company;Manageability Systems Lab
adr;dom:110 Spit Brook Rd;;ZKO2-3/Q18;Nashua;NH;03062
email;internet:david.butenhof@xxxxxx
title:HP Utility Pricing software agent Technical Lead
tel;work:603.884.7460
note;quoted-printable:POSIX thread standards consultant=0D=0A=
	Author of "Programming With POSIX Threads" (Addison-Wesley)=0D=0A=
	Father to Amy (13) and Alyssa (9)
x-mozilla-html:TRUE
version:2.1
end:vcard