From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Path: eternal-september.org!reader02.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!cleanfeed1-b.proxad.net!nnrp1-1.free.fr!not-for-mail
Subject: Re: Unchecked_Deallocation with tagged types
Newsgroups: comp.lang.ada
References: <607b56f8$0$3721$426a34cc@news.free.fr>
 <s5gq77$110s$1@gioia.aioe.org> <607bf826$0$3733$426a74cc@news.free.fr>
 <s5h02c$1ffp$1@gioia.aioe.org>
From: DrPi <314@drpi.fr>
Date: Sun, 18 Apr 2021 12:42:33 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.9.1
MIME-Version: 1.0
In-Reply-To: <s5h02c$1ffp$1@gioia.aioe.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Message-ID: <607c0d1b$0$32503$426a74cc@news.free.fr>
Organization: Guest of ProXad - France
NNTP-Posting-Date: 18 Apr 2021 12:42:35 CEST
NNTP-Posting-Host: 82.65.30.55
X-Trace: 1618742555 news-3.free.fr 32503 82.65.30.55:65336
X-Complaints-To: abuse@proxad.net
Xref: reader02.eternal-september.org comp.lang.ada:61822
List-Id: <comp.lang.ada>

Le 18/04/2021 à 12:01, Dmitry A. Kazakov a écrit :
> On 2021-04-18 11:13, DrPi wrote:
> 
>> I know Ada convention is to use Camel_Case_Syntax. Maybe there's also 
>> a convention for naming ?
>>
>> What's the convention you use for naming ?
> 
> If you use suffixes, then stick to them.
> 
>    Element_Record / Element
> 
> The above is GtkAda convention. GtkAda object types have the suffix 
> _Record, because they are used rarely. The access to object types have 
> no suffix, because they are used most.
> 
> The normal case is rather reverse, e.g.
> 
>    Element / Element_Ptr
> 
> Because access types are infrequent.
> 
> The Ada standard library tend to use _Type, e.g. File_Type, for types. 
> It works well when you have very general concepts, like 
> Root_Stream_Type, you want to stick out.
> 
> In a specific application program you would rather avoid _Type and 
> choose something descriptive, like Customer_Report. Then an instance of 
> could be more vague, like Report.
> 
> So, no convention, I would say, just common sense.
> 
And one common sense per programmer ;)

Thanks