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,c39ad3e35a7690a9
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
Received: by 10.68.222.71 with SMTP id qk7mr3865575pbc.1.1328884704071;
        Fri, 10 Feb 2012 06:38:24 -0800 (PST)
Path: 
 wr5ni8901pbc.0!nntp.google.com!news1.google.com!news4.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: Convention for naming of packages
Date: Fri, 10 Feb 2012 15:38:22 +0100
Organization: Ada @ Home
Message-ID: <op.v9gv98imule2fv@douda-yannick>
References: <op.v9fjran9ule2fv@douda-yannick> <jh1ho5$3hb$1@dont-email.me>
NNTP-Posting-Host: 3Dnc1BsVLavoSxHR9zQiRQ.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/11.61 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: Quoted-Printable
Date: 2012-02-10T15:38:22+01:00
List-Id: <comp.lang.ada>

Le Thu, 09 Feb 2012 23:35:51 +0100, J-P. Rosen <rosen@adalog.fr> a =C3=A9=
crit:
> For packages used for classes, you might consider the convention
> described in "A naming convention for packages in Ada9X", that you can=

> download from http://www.adalog.fr/publica2.htm

I remember I already read something similar. You were the author too. Th=
is  =

was about Mixin / Facet (both names were used). On my own side, I would =
 =

also suggest Aspect, as the term seems more common (think about =E2=80=9C=
Aspect  =

Programming=E2=80=9D).

I use part of the convention recommended in this paper, that's the reaso=
n  =

why I use Instance_Type in many place since long ;) This indeed end to b=
e  =

handy in the long run, and not only for the reasons exposed in the paper=
:  =

this also help readability as it emphases relationship of the main type =
 =

with the other auxiliary types defined in a package. In other words, thi=
s  =

avoid useless noise and add emphases to roles. Being constant is often  =

good (save cognitive loads), and this convention afford consistency.


-- =

=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 Univers=
ity