Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ucla-cs!zen!ucbvax!cbosgd!osu-eddie!osupyr!rwm
From: rwm@osupyr.UUCP (Robert Manson)
Newsgroups: comp.lang.c
Subject: Re: TRUE, FALSE and writing readable code...
Message-ID: <37@osupyr.UUCP>
Date: Wed, 29-Jul-87 12:53:29 EDT
Article-I.D.: osupyr.37
Posted: Wed Jul 29 12:53:29 1987
Date-Received: Sat, 1-Aug-87 04:37:02 EDT
References: <8507@brl-adm.ARPA>
Reply-To: rwm@osupyr.UUCP (Robert Manson)
Organization: Mathematical Sciences Computer Lab, Columbus, OH
Lines: 14

I'm a real novice to the net, but a somewhat experienced C programmer. I've
never had any problems with true/false values (maybe due to lack of
experience?, but it seems to me that any problems could be solved with:
	#define true(X) (X!=0)
or however one would want to define "truth".I'm not sure exactly what the
original argument was, but it seems to me that a test like:
	f(x)==TRUE
is always going to be dependent on the function, and I would say a very
bad practice (not to say somewhat machine dependent). The above #define
has the advantage that it could be varied as needed from machine to
machine.
						Bob Manson
Disclaimer: I quite possibly have no idea what anyone else is talking
about, including me.