🚀 go-pugleaf

In article <VANDEVOD.95Dec4121952@avs.cs.rpi.edu>,
   vandevod@cs.rpi.edu (David Vandevoorde) wrote:
>>>>>> "m" == mzhou01  <mzhou01@barney.poly.edu> writes:
>m> Basically I browsed the 57 C++ keywords web page and was disappointed. 
>
>the number of keywords has never been a problem to me.

Agreed, but in some places /naming consistency/ is still a big problem: e.g. 
for exception classes, the draft reads like a hodgepodge.  As a 
counterexample, I derive all my exception classes from ExBase (which is 
usually derived from the compiler's root exception class), and use consistent 
names that always start with "Ex"... simplicity itself, and you always know: 
a) which classes are exceptions; and b) what all the exception classes are 
('grep "class Ex" *.h' does it nicely).  Try that with the current draft... 
:-/

If this kind of consistency is going to make it into the standard, it's got to 
be done soon before we lose the window of opportunity simply because people 
start using the draft names and too much code would break.  In fact, we may 
already be past that point, but I'm hoping we're not.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Herb Sutter                                       Connected Object Solutions
herbs@interlog.com                                     2228 Urwin, Suite 102
                                                  Oakville ON Canada L6L 2T2
http://www.interlog.com/~herbs/           (416) 618-0184  fax (905) 847-6019



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