Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 15 Aug 2001 12:36:44 -0700
From: Wesel <wassdamo AT pacbell DOT net>
Subject: Condition Variables?
To: cygwin AT cygwin DOT com
Message-id: <3B7ACF4C.2DA7CE0@pacbell.net>
MIME-version: 1.0
X-Mailer: Mozilla 4.75 [en] (Win98; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en,ja

In my copy of the libraries (Cygwin 1.3.2) I noticed the
PTHREAD_COND_INITIALIZER macro was unfinished, and in need of fixing. 
How reliable are condition variables in cygwin?  Are they completely
broken, or is it just that one macro?

I asked about it on comp.programming.threads and was informed that "the
thread library you happen to be stuck using sort of almost pretends to
be POSIX threads but lacks critical and basic capabilities required of
any thread library."  I know we're not perfect, but cygwin is supposed
to try its darndest to provide a POSIX interface.  How would one go
about fixing the problems with condition variables?


Wesel
Who hasn't even managed to compile the cygwin source, so be gentle with
him.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/