From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 108717,ea99940253996e3e X-Google-Attributes: gid108717,public X-Google-Thread: 109fba,ea99940253996e3e X-Google-Attributes: gid109fba,public X-Google-Thread: f43e6,ea99940253996e3e X-Google-Attributes: gidf43e6,public X-Google-Thread: 103376,ea99940253996e3e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-09-28 03:17:50 PST Path: news1.google.com!newsfeed.stanford.edu!postnews1.google.com!not-for-mail From: jdallen2000@yahoo.com (James Dow Allen) Newsgroups: comp.software-eng,comp.programming,comp.lang.c++,comp.lang.ada Subject: Re: ISO Studies of underscores vs MixedCase in Ada or C++ Date: 28 Sep 2003 03:17:43 -0700 Organization: http://groups.google.com/ Message-ID: <266426e1.0309280217.15508f70@posting.google.com> References: <2cfd1a4e.0309252032.3e3c0a1a@posting.google.com> NNTP-Posting-Host: 203.150.14.161 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1064744269 27682 127.0.0.1 (28 Sep 2003 10:17:49 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 28 Sep 2003 10:17:49 GMT Xref: news1.google.com comp.software-eng:28 comp.programming:191 comp.lang.c++:418 comp.lang.ada:66 Date: 2003-09-28T10:17:49+00:00 List-Id: > On 25 Sep 2003 21:32:40 -0700, andy.glew@amd.com (Andy Glew) wrote in > comp.lang.c++: > > Specifically, are names formed with > > underscores more or less readable > > than names formed with MixedCase > > StudlyCaps camelCase? In the discussion I haven't yet seen the *correct* answer. :-) CamelMode, camel_mode, etc. are all quite *readable*; when using long names the important thing is to make them *writable*, i.e. easy to remember. Consistency is therefore the important thing. If you abbreviate words, abbreviate them as the first 4 (or whatever) letters, consistently. (I usually rewind a file with "lseek(fd, 0L, 0)" because I can't remember if 0 is SEEKSET or SEEK_SET.) James