Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool2.mu.edu!samsung!crackers!jjmhome!zinn!nuucp
From: mjv@objects.mv.com (Michael J. Vilot)
Newsgroups: comp.lang.c++
Subject: Naming Conventions
Message-ID: <1111@zinn.MV.COM>
Date: 12 Jan 91 20:48:21 GMT
Sender: nuucp@zinn.MV.COM
Lines: 21

Jim Adcock suggested X3J16 adopt a consistent approach to naming the classes in
the standard library for C++.  He also suggests a naming convention for the 
public member functions of these classes.

We discussed exactly this topic within the library group at November's meeting.
I agree with Jim that the naming is an important aspect of the usability of the
classes.  I even agree with the proposed conventions he suggested, but others
may differ.

There are other library issues to discuss, such as how we can tell (in the 
presence of inheritance and access specifiers) when a vendor's implementation
``conforms'' to the standard; and just how much of the extant I/O streams code
represents ``existing practice'' that should be supported; and how to apply
templates and exceptions to the standard library.

I hope folks will contribute their thoughts to the discussion.  comp.std.c++
seems to be a relevant forum for the discussion.

--
Mike Vilot,  ObjectWare Inc, Nashua NH
mjv@objects.mv.com  (UUCP:  ...!decvax!zinn!objects!mjv)