home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!mips!swrinde!elroy.jpl.nasa.gov!ames!network.ucsd.edu!ucsbcsl!foxtrot.ccmrc.ucsb.edu
- From: doug@foxtrot.ccmrc.ucsb.edu (Douglas Scott)
- Newsgroups: comp.lang.c++
- Subject: Re: Programming guidelines: naming of data members?
- Message-ID: <5366@ucsbcsl.ucsb.edu>
- Date: 23 Jul 92 17:08:02 GMT
- References: <1992Jul20.232457.8295@taumet.com>
- Sender: root@ucsbcsl.ucsb.edu
- Reply-To: doug@foxtrot.ccmrc.ucsb.edu
- Distribution: usa
- Lines: 24
-
- In article <1992Jul20.232457.8295@taumet.com> steve@taumet.com (Steve Clamage)
- writes:
- ] sjm@bcrki65.bnr.ca (Stuart MacMartin) writes:
- ]
- ] >Some people have suggested using the convention of prefixing data members
- ] >with an underscore, e.g. _name, _virtual and _template. This is
- recommended
- ] >by Plum & Saks in "C++ Programming Guidelines", and recommended *against*
- ] >in the Ellemtel coding standards.
- ]
- ] >I ... am also somewhat alarmed by the ARM, p.7:
- ]
- ] > Identifiers starting with a single underscore (_) should also be
- ] > avoided by ordinary users since C implementations reserve those for
- ] > their own use.
-
- I use underscores *after* the names, like length_ and name_. These conflict
- with nothing I know of.
-
- --
- Douglas Scott (805)893-8352
- Center for Computer Music Research and Composition
- University of California, Santa Barbara
- Internet: (NeXTMail ok) <doug@foxtrot.ccmrc.ucsb.edu>
-