Actions

icon Post
text/html Subscribe
text/html Unsubscribe
CodeSourcery > List Archives
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Does the cancelation exception have a name?

  • To: c++-pthreads@xxxxxxxxxxxxxxxx
  • Subject: Re: Does the cancelation exception have a name?
  • From: Alexander Terekhov <terekhov@xxxxxx>
  • Date: Mon, 06 Nov 2006 06:31:04 +0100
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."

>                              so it doesn't matter from a (standard) C++
> perspective whether it's distinct from pthread_cancel_e.
> 
> Restated, the question is what a C++ threading proposal for the next
> standard should contain with respect to the exception types:
> 
> A. nothing
> 
> B.
> 
> namespace std
> {
>     typedef /* unspecified */ thread_cancel_exception; // matches cancel and
> exit
> };
> 
> C.
> 
> namespace std
> {
>     typedef /* unspecified */ thread_cancel_exception;
>     typedef /* unspecified */ thread_exit_exception;
> };

D. 

   std::thread_termination_request (base for cancel and exit)
   std::thread_cancel_exception
   std::thread_exit_exception<T>
   std::thread_longjmp_exception

regards,
alexander.