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 Date: Wed, 27 Jun 2001 13:33:27 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: pthreads works, sorta Message-ID: <20010627133327.H22088@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <01C0FE95.54BB7F10.jorgens@coho.net> <3B3A0345.FA629136@beamreachnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3B3A0345.FA629136@beamreachnetworks.com>; from emonsler@beamreachnetworks.com on Wed, Jun 27, 2001 at 09:01:09AM -0700 On Wed, Jun 27, 2001 at 09:01:09AM -0700, Eric M. Monsler wrote: >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... You've got it right. The pointers being checked should always be writable. cgf -- 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/