🚀 go-pugleaf

In article <416oev$71f@mujibur.inmind.com>,  <mfinney@inmind.com> wrote:
>
>I personally find it very annoying to use 'true' in one location and 'True'
>or 'TRUE' or 'tRUe' somewhere else -- differing only in capitalization but
>having the same intent and semantic definition.  This is absolutely (in my
>opinion) unnecessary confusion that such a situation would engender.  And
>it would ALSO tend to promote bugs.  The preprocessor would bitch if 'true'
>were used, but the compiler would NOT bitch if 'True' were used because
>of the standard promotion rules.
>

	Unfortunately, it's even worse than that.   The preprocessor will 
NOT complain about true.   This can cause some rather unpleasant surprises,
for example:

#define MC68000

#ifdef MC68000
#define BIGENDIAN true
#endif

#if BIGENDIAN
int main(int argc, char **argv)
{
  printf("Hello, world!\n);
  return 0;
}
#else
int main(int argc, char **argv)
{
  printf("Surprise!\n);
  return 1;
}
#endif

--
William E. Aitken 			    | Formal verification is the 
email: aitken@halcyon.com                   |  future of computer science ---
Snail: 8500 148th Ave NE #H1026 Redmond WA  | Always has been, always will be.
===============================================================================

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