This is the mail archive of the
mailing list for the pthreas-win32 project.
Re: [pthread-win32] Re: pthreads on Win2k
- To: "Stephen R. Johns" <stephen dot johns at securelogix dot com>
- Subject: Re: [pthread-win32] Re: pthreads on Win2k
- From: Tristan Savatier <tristan at mpegtv dot com>
- Date: Fri, 23 Mar 2001 12:58:04 -0800
- CC: Steve Croall <SCroall at staffware dot com>,'John Funnell' <jfunnell at projectmayo dot com>,"'pthreads-win32 at sourceware dot cygnus dot com'" <pthreads-win32 at sourceware dot cygnus dot com>
- Organization: MpegTV - http://www.mpegtv.com - +1 415 864 6466
- References: <E4322E4A1C05D511851A000102B82E88024BB7@PANDORA> <3ABB5E20.firstname.lastname@example.org>
Stephen R. Johns wrote:
> Probably not related, but just in case...
> I've been trying to port a linux program to pthreadw32, and found
> a mutex issue/difference.
> Linux allows threads other than the locking thread to unlock a mutex,
> but pthreads does not.
I don't recall that the POSIX standard places a restriction on
which thread can unlock a mutex, but it does not look like good
programming style to have a mutex locked and unlocked by different
If posix-thread places a restriction that is not defined by the
standard, it should be documented. It does not look like this
one is a real problem... looks like POSIX should have put the
restriction in the standard! I suppose that the underlying win32
threads do have this restriction.