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
Message-ID:	<3B3A0345.FA629136@beamreachnetworks.com>
Date:	Wed, 27 Jun 2001 09:01:09 -0700
From:	"Eric M. Monsler" <emonsler AT beamreachnetworks DOT com>
X-Mailer:	Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	"jorgens AT coho DOT net" <jorgens AT coho DOT net>
CC:	"Cygwin List (E-mail)" <cygwin AT cygwin DOT com>
Subject:	Re: pthreads works, sorta
References:	<01C0FE95 DOT 54BB7F10 DOT jorgens AT coho DOT net>

Steve Jorgensen wrote:
> 
> OK, I'm over my head to even try to participate in this, but it seems to me
> that if you want to check for the condition where you can neither read nor
> write

I think that the check is for the condition that "one can both read and
write", before proceeding.  The IsBad logic forces a somewhat reversed
logical structure, i.e. "if not both read and write, fail", which is
coder-optimised to "if not write, fail", since if we can't read we also
can't write.

Read-only is failure, as is a NULL, or any other bad pointer.

Assuming I've understood the previous discussions correctly...


Eric Monsler

--
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/

- Raw text -