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,cfb2002511b830ab
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
Received: by 10.68.59.229 with SMTP id c5mr20632508pbr.6.1322405525095;
        Sun, 27 Nov 2011 06:52:05 -0800 (PST)
Path: 
 lh20ni24214pbb.0!nntp.google.com!news2.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!usenet-fr.net!gegeweb.org!aioe.org!.POSTED!not-for-mail
From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?=
 =?utf-8?Q?=29?=
 <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re: Starter project: getopt_long in Ada
Date: Sun, 27 Nov 2011 15:52:03 +0100
Organization: Ada @ Home
Message-ID: <op.v5l0w1ztule2fv@douda-yannick>
References: <slrnjcushg.vl6.lithiumcat@sigil.instinctive.eu>
 <op.v5lh23k4ule2fv@douda-yannick>
 <slrnjd4bqu.vl6.lithiumcat@sigil.instinctive.eu>
NNTP-Posting-Host: B0fj88Qo5RPyajGtdWC/cQ.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/11.60 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news2.google.com comp.lang.ada:14682
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: Quoted-Printable
Date: 2011-11-27T15:52:03+01:00
List-Id: <comp.lang.ada>

Le Sun, 27 Nov 2011 13:39:03 +0100, Natasha Kerensikova  =

<lithiumcat@gmail.com> a =C3=A9crit:
> On the other hand, Options_DB reminds of the wild abbreviations in my =
C
> life. Option_Database maybe?
There is difference between an abbreviation only the writer know what it=
  =

means, and an abbreviation everyone know what it means. If abbreviations=
  =

are uncommon in Ada prose, this is not because Ada users hate  =

abbreviations, but because they don't like things others can't read.

DB is a well know word, and every one will read it as Data_Base, except =
in  =

an audio processing application.

Similarly, they is no fear to have to write HTML and not  =

Hyper_Text_Markup_Language, which on the opposite, would deserve  =

readability. When possible, shorter is better (while the choice of a goo=
d  =

name, also vary depending on the scope size).

> Or Option_Container? But isn't that a bit too implementation-oriented,=

It's up to you, you are the author :) , I just feel you can get ride of =
 =

the word Option in this name, as this is already implied by the package =
 =

name. Not the same for an Option parameter, standing for an option,  =

solely. What I like with the word DB here, is that it underline the  =

specific role while being short.

But please, keep in mind this is just my feeling.

-- =

=E2=80=9CSyntactic sugar causes cancer of the semi-colons.=E2=80=9D [1]
=E2=80=9CStructured Programming supports the law of the excluded muddle.=
=E2=80=9D [1]
[1]: [Epigrams on Programming =E2=80=94 Alan J. =E2=80=94 P. Yale Univer=
sity]