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.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,d2bfd9e7e44fbefe X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 Received: by 10.224.181.75 with SMTP id bx11mr8418109qab.7.1347409419359; Tue, 11 Sep 2012 17:23:39 -0700 (PDT) Path: q11ni19666166wiw.1!nntp.google.com!feeder3.cambriumusenet.nl!feeder1.cambriumusenet.nl!feed.tweaknews.nl!94.232.116.12.MISMATCH!feed.xsnews.nl!border-2.ams.xsnews.nl!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newsgate.cuhk.edu.hk!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: Manuel Collado Newsgroups: comp.lang.ada Subject: Re: Ada's identifiers casing considered ugly Date: Wed, 05 Sep 2012 23:07:25 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <5047a6c6$0$6168$ba4acef3@reader.news.orange.fr> NNTP-Posting-Host: v+ytDY5AIoJxo8sOnL58nA.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: 2012-09-05T23:07:25+02:00 List-Id: El 05/09/2012 21:37, Vinzent Hoefler escribió: > Pascal Obry wrote: > >> Le 05/09/2012 21:01, Yannick Duchêne (Hibou57) a écrit : >>> (this topic is for fun) >>> >>> I was reading the Python's PEP‑8, which I have not read so far, when >>> just saw this: >>> >>> http://www.python.org/dev/peps/pep-0008/ >>> >>> > The following naming styles are commonly distinguished: >>> > […] >>> > Capitalized_Words_With_Underscores (ugly!) >> >> iunderstandthemasitisreallyhardtoreadatextwithunderscoresseparatingwords. > > AndItSureDoesNotLookSoUgly. Ada code is case insensitive. So a code reformatter can safely change the case of identifiers to a normalized form, in order to avoid variants of the same identifier inside a set of source files. If there are no underscores to delimit components of a composed identifier, then they can/should be merged in a single word. Underscores as separators ensure that the composed name remains a composed one. After that, capitalization of individual components of a composed identifier remains a matter of taste. Some people will find it easier to read (w.r.t. all lowercase or uppercase). Just my 2c. -- Manuel Collado - http://lml.ls.fi.upm.es/~mcollado