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: a07f3367d7,25d835bb9a4a003f
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,CP1252
Path: 
 g2news2.google.com!postnews.google.com!l2g2000yqd.googlegroups.com!not-for-mail
From: =?ISO-8859-1?Q?Hibou57_=28Yannick_Duch=EAne=29?=
 <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re: Types, packages & objects : the good old naming conventions
	question (without religious ware)
Date: Thu, 29 Oct 2009 22:28:33 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: <e49885cb-395c-4bca-9f70-a66b7da5a3b2@l2g2000yqd.googlegroups.com>
References: 
 <ae7fb66b-4eff-405f-b568-77a1047ec6cb@n35g2000yqm.googlegroups.com>
	<4ae9dade$0$6551$9b4e6d93@newsspool4.arcor-online.net>
 <561e0a4a-c6c0-42db-9f31-a70f4eae1ed9@a21g2000yqc.googlegroups.com>
	<hcdsbv$tad$1@news.tornevall.net>
NNTP-Posting-Host: 86.75.149.92
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1256880513 5504 127.0.0.1 (30 Oct 2009 05:28:33
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 30 Oct 2009 05:28:33 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: l2g2000yqd.googlegroups.com; posting-host=86.75.149.92;
	posting-account=vrfdLAoAAAAauX_3XwyXEwXCWN3A1l8D
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
	fr),gzip(gfe),gzip(gfe)
Xref: g2news2.google.com comp.lang.ada:8875
Date: 2009-10-29T22:28:33-07:00
List-Id: <comp.lang.ada>

On 30 oct, 06:08, "Jeffrey R. Carter" <spam.jrcarter....@spam.acm.org>
wrote:
> I think that you shouldn't be writing anything until you've decided on th=
e type
> and its operations, including their parameters.
>
> This isn't trouble. A type is usually only part of what you're creating, =
and
> it's important to think about the whole thing before committing any part =
of it
> to code. This is especially true for the visible part of a pkg spec.

That's a good note (in my mind, I was thinking about any context, but
its clear that the one you've pointed is particularly important and
should be guiding).

So let's go further the standalone concept of naming convention, and
add a seed of method, which may say =93 name a type and its instance
names in primitives, all together (and the remaining should be OK) =94

:)