Path: utzoo!attcan!uunet!auspex!guy
From: guy@auspex.UUCP (Guy Harris)
Newsgroups: comp.lang.c
Subject: Re: Definition of boolean type
Message-ID: <1096@auspex.UUCP>
Date: 1 Mar 89 18:51:38 GMT
References: <10@dbase.UUCP> <1989Feb10.092449.20875@sq.uucp> <6849@pogo.GPID.TEK.COM>
Reply-To: guy@auspex.UUCP (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 14


 >With the compiler I am currently using, I use "if (x == FALSE)" or
 >"if (x != FALSE).  This doesn't have an ambiguity because of multiple
 >true values.  The compiler I am using generates LESS code this way. 
 >("if (x)" causes it to go to the work of converting it to a 1 or 0
 >with some less than efficient code.  That is ignoring the fact the
 >whole process it unneeded.)

Yup, it sure is unneeded.  Why is the compiler in question so dumb?

 >PROM space is tight, so this becomes important.

Are there any smart compilers for the chip in question?  If so, you
might want to pick them up, given that PROM space *is* so tight....