Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!nx02.iad01.newshosting.com!newshosting.com!post01.iad!post02.iad!not-for-mail X-newsreader: xrn 9.03-beta-14-64bit Sender: scott@lews (Scott Lurndal) From: scott@slp53.sl.home (Scott Lurndal) Reply-To: slp53@pacbell.net Subject: Re: POSIX threads hard to implement in Windows Newsgroups: comp.lang.c,comp.programming.threads,comp.unix.programmer References: <4e116c59$0$13719$426a34cc@news.free.fr> <97ek3iFq2bU2@mid.individual.net> <4e13c801$0$20925$a729d347@news.telepac.pt> <4e13d4a7$0$20921$a729d347@news.telepac.pt> <37pfe8-4gl.ln1@jones.homeip.net> Organization: Keywords: Organization: UseNetServer - www.usenetserver.com X-Complaints-To: abuse@usenetserver.com Message-ID: Date: 11 Jul 2011 16:18:17 GMT Lines: 25 Xref: x330-a1.tempe.blueboxinc.net comp.lang.c:8135 comp.programming.threads:421 comp.unix.programmer:935 lawrence.jones@siemens.com writes: >William Ahern wrote: >> >> POSIX threads can be implemented quite comprehensively on Windows: >> >> http://sourceware.org/pthreads-win32/conformance.html > >Then why is there a long list of unimplemented functions? Certainly >there are *parts* of pthreads that can be implemented on Windows, but >that's not the same thing as implementing the whole thing. A quick examination of the list of functions concludes that they fit into one of the following categories: - Not applicable to windows (pthread_atfork, getpwnam_r, et. al.) - An optional POSIX feature (robust mutexes) - stdio & C Library extensions - signals It looks like cancellation points are the most difficult feature of pthreads to implement on windows - this reference notes that the application must explictly code the cancellation points into the application using non-standard API's. scott