public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Tristan Savatier <tristan@mpegtv.com>
To: "Stephen R. Johns" <stephen.johns@securelogix.com>
Cc: Steve Croall <SCroall@staffware.com>,
	'John Funnell' <jfunnell@projectmayo.com>,
	"'pthreads-win32@sourceware.cygnus.com'"
	<pthreads-win32@sourceware.cygnus.com>
Subject: Re: [pthread-win32] Re: pthreads on Win2k
Date: Fri, 23 Mar 2001 12:58:00 -0000	[thread overview]
Message-ID: <3ABBB8DC.755ADDCE@mpegtv.com> (raw)
In-Reply-To: <3ABB5E20.9040508@securelogix.com>

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
threads..

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.

-t

  parent reply	other threads:[~2001-03-23 12:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-23  1:35 Steve Croall
2001-03-23  6:31 ` Stephen R. Johns
2001-03-23  6:54   ` Scott McCaskill
2001-03-23  7:13     ` Stephen R. Johns
2001-03-23 12:58   ` Tristan Savatier [this message]
2001-03-23 13:35 [pthread-win32] " Bossom, John
2001-03-23 15:58 ` Ross Johnson
2001-03-23 17:21 Bossom, John

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ABBB8DC.755ADDCE@mpegtv.com \
    --to=tristan@mpegtv.com \
    --cc=SCroall@staffware.com \
    --cc=jfunnell@projectmayo.com \
    --cc=pthreads-win32@sourceware.cygnus.com \
    --cc=stephen.johns@securelogix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).