Remove TRUE and FALSE

David Korn dkorn@pixelpower.com
Tue Feb 27 02:44:00 GMT 2001


>-----Original Message-----
>From: Fergus Henderson [ mailto:fjh@cs.mu.oz.au ]
>Sent: 27 February 2001 06:41

>> I'm ambivalent about the change.  On the one hand, it is consistent
>> with the rest of the compiler.  On the other, I do feel that use of
>> TRUE and FALSE provides information to readers which 1 and 0 don't.
>> On the third hand, if we want to keep them, we ought to be moving
>> toward <stdbool.h> [or fake thereof] anyway.
>
>I'm opposed to the change, for the reason that you give above.
>In the long term, I'd like the rest of the compiler to change
>from using 0 and 1.  Of course this would be a lot of work
>(and I'm not volunteering), but I'd prefer inconsistent use of 1/0
>in some parts and true/false in others to using 1/0 everywhere.
>The parts which use 1/0 will still have the same information
>as now, and the parts using true/false will be easier to read.

  Isn't #defining TRUE just asking for future trouble because sooner
or later somebody is liable to write "if ((condition) == TRUE)" ?  And
if so, doesn't that really mean that the only use of TRUE is for 
initializing variables?  

       DaveK
-- 
"Never give succor to the mentally ill; it is a bottomless pit."  
  -- William S. Burroughs


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************



More information about the Gcc-patches mailing list