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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no 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.39.100 with SMTP id o4mr20203536pbk.0.1322397543675;
        Sun, 27 Nov 2011 04:39:03 -0800 (PST)
Path: 
 lh20ni23867pbb.0!nntp.google.com!news2.google.com!news.glorb.com!feeder.erje.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Natasha Kerensikova <lithiumcat@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Starter project: getopt_long in Ada
Date: Sun, 27 Nov 2011 12:39:03 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <slrnjd4bqu.vl6.lithiumcat@sigil.instinctive.eu>
References: <slrnjcushg.vl6.lithiumcat@sigil.instinctive.eu>
 <op.v5lh23k4ule2fv@douda-yannick>
Mime-Version: 1.0
Injection-Date: Sun, 27 Nov 2011 12:39:03 +0000 (UTC)
Injection-Info: mx04.eternal-september.org;
 posting-host="Mda950WjNwNLAFOE7yJXQw";
	logging-data="5352"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18k5xixVoKdCaSgAkWujefG"
User-Agent: slrn/0.9.9p1 (FreeBSD)
Cancel-Lock: sha1:dtyOt54Mu1IVQKvR0FfziEbTECc=
Xref: news2.google.com comp.lang.ada:14680
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Date: 2011-11-27T12:39:03+00:00
List-Id: <comp.lang.ada>

Hello,

On 2011-11-27, Yannick Duchêne <yannick_duchene@yahoo.fr> wrote:
> “Option_Definitions” may be renamed into “Options_DB”, and parameters  
> named “Options” into “DB” for more clarity. Just a personal feeling, I  
> don't assert anything.

Thanks for the suggestion. I was uncomfortable with Option_Definitions
because I usually use singular nouns for type names. I tried things like
Option_List, but it's not a list in a CS sense.

On the other hand, Options_DB reminds of the wild abbreviations in my C
life. Option_Database maybe?

Or Option_Container? But isn't that a bit too implementation-oriented,
the client probably cares more about the function of the object than
about the kind of stuff that exists inside, so shouldn't the type name
reflect client's point of view?


Thanks for ponting it out,
Natasha