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 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: f43e6,ea99940253996e3e X-Google-Attributes: gidf43e6,public X-Google-Thread: 109fba,ea99940253996e3e X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,ea99940253996e3e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-09-27 04:18:51 PST Path: news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!fu-berlin.de!uni-berlin.de!dialup-151.116.220.203.acc01-coll-hbt.comindico.com.AU!not-for-mail From: Mad Hamish 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: Sat, 27 Sep 2003 21:18:45 +1000 Message-ID: References: <2cfd1a4e.0309252032.3e3c0a1a@posting.google.com> NNTP-Posting-Host: dialup-151.116.220.203.acc01-coll-hbt.comindico.com.au (203.220.116.151) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de 1064661528 8035772 203.220.116.151 (16 [145588]) X-Newsreader: Forte Agent 1.93/32.576 English (American) Xref: news1.google.com comp.software-eng:1 comp.programming:28 comp.lang.c++:46 comp.lang.ada:6 Date: 2003-09-27T21:18:45+10:00 List-Id: On Fri, 26 Sep 2003 15:40:00 GMT, "Frank J. Lhota" wrote: >Underscores are basically a way to provide spaces in an identifier. Since >identifiers are generally phrases (nown phrases for objects, verb phrases >for procedures) and phrases often consist of more than one word, I find the >use of underscores to be quite natural. > >The opposing argument is that underscores are too large, and that a case >change is a more readable way to indicate how to divide the decomposition >into words. To me, the upper / lower case method of delineate the words in >an indentifier has always looked like the transcript of a very fast talker. >Yes, you can make out the words, but just barely. Moreover, the use of >letter case to delineate words prohibits any other use of letter case. It >rules out using all caps for a certain category of identifiers, for example. > >There is an easy way to test which convention is more readable. Here is one >of Shakespeare's sonnets rendered in the mixed case format: > > FromFairestCreaturesWeDesireIncrease, > ThatTherebyBeautysRoseMightNeverDie, > ButAsTheRiperShouldByTimeDecease, > HisTenderHeirMightBearHisMemory: > ButThouContractedToThineOwnBrightEyes, > FeedstThyLightsFlameWithSelfSubstantialFuel, > MakingAFamineWhereAbundanceLies, > ThySelfThyFoeToThySweetSelfTooCruel: > ThouThatArtNowTheWorldsFreshOrnament, > AndOnlyHeraldToTheGaudySpring, > WithinThineOwnBudBuriestThyContent, > AndTenderChurlMakstWasteInNiggarding: > PityTheWorldOrElseThisGluttonBe, > ToEatTheWorldsDueByTheGraveAndThee > >It may be a matter of taste, but I certainly found the original sonnet to be >more readable and more beautiful. > But produces more compilation errors. Hence the mixed case format must be better for programming. -- "Hope is replaced by fear and dreams by survival, most of us get by." Stuart Adamson 1958-2001 Mad Hamish Hamish Laws h_laws@aardvark.net.au