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-Thread: 103376,429176cb92b1b825 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 Path: g2news2.google.com!news4.google.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!193.201.147.68.MISMATCH!feeder.news-service.com!94.75.214.39.MISMATCH!aioe.org!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: AWS Coding Styles (and about boring plain-linear text files in the end) Date: Tue, 18 Jan 2011 23:16:11 +0100 Organization: Ada @ Home Message-ID: References: <24418fa4-8843-4fe6-8c2f-026ea6009b68@g26g2000vbz.googlegroups.com> <87lj2ido9j.fsf@mid.deneb.enyo.de> <4dc188a3-468c-40eb-9f3c-85bfb621cb23@o14g2000prn.googlegroups.com> NNTP-Posting-Host: 59xjXE7stDARAmb8zI1USw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 User-Agent: Opera Mail/11.00 (Win32) Xref: g2news2.google.com comp.lang.ada:17506 Date: 2011-01-18T23:16:11+01:00 List-Id: Le Tue, 18 Jan 2011 20:47:26 +0100, Adam Beneschan a = =C3=A9crit: > Maybe that's what the style guide author intended. If so, I think he > had it completely backward. Look at the RM's descriptions of what the= > subprograms in language-defined packages do, and then try to figure > out how to describe them without referring to parameter names. Try > Ada.Strings.Unbounded.To_String and To_Unbounded_String, for example, > in A.4.5(78-79). That's just the first thing I went to when I picked > an Annex A section more or less arbitrarily---I didn't have to hunt > for the "best example". Anyway, you *could* rewrite the description > in a way that doesn't refer to the parameter names, but all you gain > is verbosity and stilted-sounding language---at the expense of > clarity, readability, and several dozen of your readers' brain cells. This raise (one more time) the question of comment consistency with = source. We really need a standard convention to mark program identifiers= = in comments (and corollary to precisely define scope of comments). -- = Si les chats miaulent et font autant de vocalises bizarres, c=E2=80=99es= t pas pour = les chiens. =E2=80=9CI am fluent in ASCII=E2=80=9D [Warren 2010]