Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3B3A0345.FA629136@beamreachnetworks.com> Date: Wed, 27 Jun 2001 09:01:09 -0700 From: "Eric M. Monsler" X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "jorgens@coho.net" CC: "Cygwin List (E-mail)" Subject: Re: pthreads works, sorta References: <01C0FE95.54BB7F10.jorgens@coho.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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/