Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!nbires!vianet!devine
From: devine@vianet.UUCP (Bob Devine)
Newsgroups: comp.lang.c
Subject: Re: Defining TRUE and FALSE
Message-ID: <205@vianet.UUCP>
Date: Wed, 15-Jul-87 14:40:47 EDT
Article-I.D.: vianet.205
Posted: Wed Jul 15 14:40:47 1987
Date-Received: Sat, 18-Jul-87 01:35:45 EDT
References: <13851@watmath.UUCP>
Organization: Western Digital, Boulder Tech Ctr
Lines: 15

In article <13851@watmath.UUCP>, jyegiguere@watmath.UUCP (Eric Giguere) writes:
> The way we define these at the Computer Systems Group here at UW
> (which we include in the  file for Waterloo C)
> is:
>           #define TRUE   ( 0 == 0 )
>           #define FALSE  ( 1 == 0 )

  This doesn't really gain you much.  FALSE is still recognized as 0
and TRUE can only be defined as non-zero.  Having the compiler fill in
the blanks is no step forward.

  For those who wrote code as "if (such_and_such == TRUE)" believing it
to really mean "if (such_and_such != FALSE)", the above does nothing.

Bob Devine