🚀 go-pugleaf

The arguments for and against making the preprocessor recognize true and
false seem to be:

For:
  1) Why not?
  2) Uniformity
Against:
  1) Why bother?

I have personally encountered a case where it would have been nice for the
preprocessor to recognize true and false:  Rogue Wave Tools.h++ uses 
a typedef RWBoolean and macros TRUE and FALSE for dealing with boolean
values.  I tried converting it over to using the bool type one day, by
replacing 'int' with 'bool' in the typedef and '1' and '0' with 'true' and
'false'.  This worked fine for actual code that used the TRUE and FALSE
macros, but where they appeared in preprocessor directives I had to replace
them with something else.  Why should this be necessary?

Jason

---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]