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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no 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: 103376,ea99940253996e3e X-Google-Attributes: gid103376,public X-Google-Thread: f43e6,ea99940253996e3e X-Google-Attributes: gidf43e6,public X-Google-ArrivalTime: 2003-09-29 11:26:07 PST Path: news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!lnewsoutpeer00.lnd.ops.eu.uu.net!lnewsinpeer00.lnd.ops.eu.uu.net!bnewsoutpeer00.bru.ops.eu.uu.net!bnewsinpeer01.bru.ops.eu.uu.net!bnewspost00.bru.ops.eu.uu.net!emea.uu.net!businessnews.de.uu.net!not-for-mail Newsgroups: comp.software-eng,comp.programming,comp.lang.c++,comp.lang.ada Subject: Re: ISO Studies of underscores vs MixedCase in Ada or C++ Reply-To: bauhaus@futureapps.de References: <2cfd1a4e.0309252032.3e3c0a1a@posting.google.com> From: Georg Bauhaus Date: 29 Sep 2003 19:34:42 +0200 Message-ID: <863cefjy6l.fsf@strudel.futureapps.de> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: 193.102.189.176 X-Trace: 1064859964 businessnews.de.uu.net 274 193.102.189.176 X-Complaints-To: abuse@de.uu.net Xref: news1.google.com comp.software-eng:53 comp.programming:422 comp.lang.c++:999 comp.lang.ada:193 Date: 2003-09-29T19:34:42+02:00 List-Id: >>>>> "Frank" == Frank J Lhota writes: : 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. But we should, I think, consider non-phrases or almost-non-phrases being used as identifiers, and "juxtapositions" of identifiers. The isolated identifiers might be shorter and thus more easily broken into parts during the "reading process". theFools(42); the_fools (42); the_Fools(42); The_Fools (42); ... y := doYouMind.ifI(); y := do_you_mind.if_i (); y := do_You_Mind.if_I(); y := Do_You_Mind.If_I (); takeAction(doYouMind.ifI(openTheWindow)); take_action (do_you_mind.if_i (open_the_window)); take_Action (do_You_Mind.if_I(open_The_Window)); Take_Action (Do_You_Mind.If_I (Open_The_Window)); So in context, your "Shakespearean" argument might still apply, even if short identifiers are readable in dense mixed case? : 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, Also, looking closely at letters, fonts certainly do matter. In a string such as "glubf()" it might or might not be easy to distinguish the two characters 'f' and '('. It depends on how ink would be spread, or on how pixels would appear on some display screen. You can see this comparing foo(a) and oof(a), using different fonts for the letters and symbols. Georg