Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!bywater!arnor!watson!blinn.watson.ibm.com!mittle
From: mittle@blinn.watson.ibm.com (Josh Mittleman)
Newsgroups: comp.lang.c++
Subject: Re: Boolean confusion
Message-ID: <1991May29.145100.18519@watson.ibm.com>
Date: 29 May 91 14:51:00 GMT
References: <HAYDENS.91May23103233@natasha.juliet.ll.mit.edu> <332@nazgul.UUCP>
Sender: @watson.ibm.com
Distribution: comp.lang.c++
Organization: IBM T. J. Watson Research
Lines: 15


> Note that you also need to get rid of any TRUE or FALSE #define's.
Remember to
> always test for 0 or !=0.
> 
> (Some other battle-scarred old C programmers have told me that they have
>  eventually come to the same conclusions.)

But that's exactly the point: Testing for == 0 is the perfect C approach,
but it entirely inconsistent with the logic of C++.  C++ should have a
standard built-in Boolean type.

===========================================================================
Josh Mittleman (mittle@watson.ibm.com or joshua@paul.rutgers.edu)
J2-C28 T.J. Watson Research Center, PO Box 704, Yorktown Heights, NY  10598