[c++-pthreads] Re: concrete library-code example

[Dave Butenhof]

David Abrahams wrote:

>Dave Butenhof <David.Butenhof at hp.com> writes:
>  
>
>>And I'm deliberately discounting the mention I've seen several times
>>in this list of "thread-safe" libraries that aren't
>>"cancel-safe". Such libraries are simply broken, from basic
>>design. Cancellation is a basic and important part of the POSIX thread
>>model, and if you're not safe you're not safe.
>>    
>>
>Do any other threading models count?
>  
>
On a discussion list titled explicitly "c++-pthreads", I automatically 
presumed not, without really giving it much thought.

But, as I said, I was completely overwhelmed with the flood of messages 
when I returned from vacation yesterday, and I SHOULD have recalled 
previous discussions on this subject that pointed out you really didn't 
intend to target "pthreads" specifically. (I.e., this mailing list is 
inappropriately named.)

You're basically talking about Win32 or UI threads (which essentially is 
legacy Solaris code), being converted trivially to "native C++ 
threading" environment. Is that a realistic limitation on your model? If 
you say so, hey, I'm not in a position to argue about your goals.

-- 
/--------------------[ David.Butenhof at hp.com ]--------------------\
| Hewlett-Packard Company       Tru64 UNIX & VMS Thread Architect |
|     My book: http://www.awl.com/cseng/titles/0-201-63392-2/     |
\----[ http://homepage.mac.com/dbutenhof/Threads/Threads.html ]---/