X-Spam-Check-By:	sourceware.org
Date:	Sun, 21 Jan 2007 06:37:31 -0800
From:	Christopher Layne <clayne AT anodized DOT com>
To:	cygwin AT cygwin DOT com
Subject:	cygwin source question
Message-ID:	<20070121143731.GC25379@ns1.anodized.com>
Mime-Version:	1.0
User-Agent:	Mutt/1.5.11
X-Assp-Spam-Prob:	0.00000
X-Assp-Whitelisted:	Yes
X-Assp-Envelope-From:	clayne AT ns1 DOT anodized DOT com
X-Assp-Intended-For:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

I notice in some places, there are double-negates, like:

me->read_ready |= ret || !!(events & (FD_READ | FD_ACCEPT | FD_CLOSE));

What's the rationale for these? To enforce either a 0 or 1, to be directly
in line with boolean, rather than a zero or non-zero result?

-cl

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -