Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!jarthur!uunet!crdgw1!underdog!volpe
From: volpe@underdog.crd.ge.com (Christopher R Volpe)
Newsgroups: comp.lang.c
Subject: Re: TRUE and FALSE
Message-ID: <11474@crdgw1.crd.ge.com>
Date: 30 Aug 90 17:16:00 GMT
References: <11215@alice.UUCP> <514@demott.COM> <2316@cirrusl.UUCP> <3835@sactoh0.SAC.CA.US> <26280@mimsy.umd.edu>
Sender: news@crdgw1.crd.ge.com
Reply-To: volpe@underdog.crd.ge.com (Christopher R Volpe)
Lines: 13

I wouldn't use TRUE and FALSE in comparisons such as if (x==TRUE)
for the reasons Chris Torek outlined, but I think they are useful
for setting default values, e.g. "int expert_mode = TRUE;".

For tests, if you want the extra clarity, how about the following:
#define TRUE(x) (x)
#define FALSE(x) (!(x))

and then do things like " if (FALSE((x==y) && (x==z)) || whatever) ..."
==================
Chris Volpe
G.E. Corporate R&D
volpecr@crd.ge.com