Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Date:	Sun, 23 Sep 2001 22:34:46 -0700 (PDT)
From:	Matt <matt AT use DOT net>
X-Sender:	<matt AT cesium DOT clock DOT org>
To:	Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
Cc:	Jason Tishler <jason AT tishler DOT net>, <cygwin-developers AT cygwin DOT com>
Subject:	RE: 1.3.4?
In-Reply-To:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF7A34@itdomain002.itdomain.net.au>
Message-ID:	<Pine.NEB.4.30.0109232231580.24214-100000@cesium.clock.org>
MIME-Version:	1.0

On Mon, 24 Sep 2001, Robert Collins wrote:

> > I'm leaning toward holding off releasing a threaded Python until your
> > muto upgrade in complete.  Do you concur?
>
> There's more than the muto change to make it "good". The second
> statement (the wait) and other threads calling the signal() clause need
> to be protected from each other. What that requires is a lock _that is
> reset when the wait function is called_. This does not exist on 95 at
> all (No SignalObjectAndWait). On NT that cannot be done for
> CriticalSections at all, so I'm going to have to find somewaht to create
> SignalMutoAndWait. I've some ideas, but nothing concrete just yet. (Any
> realtime programmers want to pop up and offer some ring 3 assembler to
> achieve this?)

MSDN says MsgWaitForMultipleObjects can be used instead of
SignalObjectAndWait in certain circumstances. While it doesn't support
Critical Sections, it is supported on win9x.

--
http://www.clock.org/~matt

- Raw text -