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-Thread: 103376,fd4fc3d2b22df500
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.68.197.201 with SMTP id iw9mr8514694pbc.6.1357362826782;
        Fri, 04 Jan 2013 21:13:46 -0800 (PST)
MIME-Version: 1.0
Path: 
 6ni82910pbd.1!nntp.google.com!news.glorb.com!feeder.erje.net!us.feeder.erje.net!newsfeed.straub-nv.de!reality.xs3.de!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: On Style: Any opinions on *not* capitalising the first letter of
 verbs in a procedure name ?
Date: Fri, 4 Jan 2013 23:13:41 -0600
Organization: Jacob Sparre Andersen Research & Innovation
Message-ID: <kc8cq9$fvd$1@munin.nbi.dk>
References: <ebe4dd4a-3473-4d3f-9cbd-72e1d5805ae8@googlegroups.com>
 <c9b71bb6-0aa9-4c31-b3d6-380eab0f4c2b@googlegroups.com>
 <wccvcbca02b.fsf@shell01.TheWorld.com>
NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net
X-Trace: munin.nbi.dk 1357362825 16365 69.95.181.76 (5 Jan 2013 05:13:45 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Sat, 5 Jan 2013 05:13:45 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Date: 2013-01-04T23:13:41-06:00
List-Id: <comp.lang.ada>

"Robert A Duff" <bobduff@shell01.TheWorld.com> wrote in message 
news:wccvcbca02b.fsf@shell01.TheWorld.com...
...
> As to whether your "reserve_Capacity" style is good or bad:
> It's not what everyone else does, so it's not a good idea.
> I suggest you save your creativity for higher-level stuff, like
> interesting algorithms and abstractions.  For low-level stuff
> like indentation and casing, just blindly do what everybody else does.
> That makes the code more readable for everybody.

That makes sense, other than "what everybody else does" is not well-defined. 
There still seems to be a lot of code in the Ada 83 style around, just to 
take one example.

At RR Software, our style guide recommends using "Title Case" for 
identifiers. That is, capitalize an identifier the same way as you would a 
title. (Our pretty printer will automatically use this style if requested.)

For instance, taking some examples from one of the AI tools:

    procedure Put_AI_Header_and_Subject (Fyle : in Ada.Text_IO.File_Type;
                                                                    Issue : 
in AI_Types.AI_Identifier) is
        -- Put a line containing an AI identifier, version,
        -- last modification date, and subject to Fyle.

   procedure Records_of_Response (TXT_Name, RTF_Name, HTML_Name : in 
String);
       -- Create the record of response document from the data stored in
       -- AI_Data.AI_Database and the original AI files.

I'm forever getting in trouble with people like Bob when I write identifiers 
in this style in the Ada Standard. :-) To me, capitalizing "_And_" and 
"_Of_" is ugly. (It should be noted, this was not originally my idea, it 
took a lot of convincing originally.)

I think the best advice is to use whatever typographical style that makes 
sense in your organization. But try to make sure that everyone that works on 
a project uses the same style! It's that consistency that counts most, not 
the details.

                                              Randy.