🚀 go-pugleaf

In <4alt1o$13a2@news.ccit.arizona.edu>, jychen@aruba.ccit.arizona.edu (Joseph Y Chen) writes:
>I have not objection to boolean type.  But those added key words like 
>and, or, xor, etc,  just make C/C++ awful, reminding me of Basic which 
>has far too many key wods.  I agree that people using C/C++ aren't fools 
>and they don't need those added key words.

I have defined "and", "or" and "not" in a project standard header
file for many years now.  I find the code is substantially more
readable than && || and ! and I don't consider myself a fool.  And I
would replace = by <- and == by = in a  heartbeat if the preprocessor
could handle it.  C/C++ has a lot of good features, but sometimes the
operators that were selected during language design are not exactly
the best in the world.

And, far more important than readablility at this level, is the problem
that C/C++ does not yet require Unicode support and so international
programs get really hairy if you have to use tri-graphs (or even the
new bi-graphs).

Michael Lee Finney


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