🚀 go-pugleaf

In article <MATT.95Aug22012318@Austern> mfinney@inmind.com writes:
>
> In <ROBERT.95Aug21123621@mirage.visix.com>, robert@Visix.COM (Robert Mollitor) writes:
> >But if the preprocessor doesn't "understand" 'true' and 'false', then what
> >stops someone from defining
> >
> >  #define true 1
> >  #define false 0
>
> That does not work correctly because if you have a function...
>
>    void foo(bool);
>    void foo(int);
>
> and you call...
>
>    foo(true)
>
> the wrong function will be called.
>

I'm sorry.  I was too cryptic.  I agree with you that it is a bad thing
for the reason you mention.  I would expect a C++ preprocessor to disallow
the #defines in the first place (as it maybe should disallow #defines to
any keyword?).  If this is a C incompatibility issue, so be it.

  #ifndef __cplusplus
  #define true 1
  #define false 0
  #endif

is easy enough.


robt
--
Robert Mollitor						      robert@visix.com
Visix Software Inc.					...!uupsi!visix!robert

[ 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. ]