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,158ce2376534c35d
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!y24g2000yqb.googlegroups.com!not-for-mail
From: AdaMagica <christ-usch.grein@t-online.de>
Newsgroups: comp.lang.ada
Subject: Re: Derived private interface
Date: Wed, 6 Jul 2011 06:23:41 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: 
 <7c515c1d-d170-4cd2-8702-6532e09d6f42@y24g2000yqb.googlegroups.com>
References: 
 <27656578-65aa-48b9-9f89-4ebd4e0cb02a@glegroupsg2000goo.googlegroups.com>
 <0fe3b0f8-c064-444d-899d-640e891b58c3@w4g2000yqm.googlegroups.com>
 <128d8eb5-1cc6-47e3-a09b-b53a5ef289ce@m10g2000yqd.googlegroups.com>
 <4e141501$0$6629$9b4e6d93@newsspool2.arcor-online.net>
 <4b2728fc-6127-45d8-a314-9fc491701c26@g12g2000yqd.googlegroups.com>
 <4e145c3a$0$6542$9b4e6d93@newsspool4.arcor-online.net>
NNTP-Posting-Host: 80.156.44.178
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1309959561 21852 127.0.0.1 (6 Jul 2011 13:39:21
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 6 Jul 2011 13:39:21 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: y24g2000yqb.googlegroups.com; posting-host=80.156.44.178;
 posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: HUALESRCNK
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 5.2; WOW64;
 rv:5.0) Gecko/20100101 Firefox/5.0,gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:20092
Date: 2011-07-06T06:23:41-07:00
List-Id: <comp.lang.ada>

I guess this has to be based on visibility to prevent privacy
breaking. In these cases where overriding indicators are illegal in
the spec, they can be applied in the body.

Note that the RM does not make any statement whether they shall appear
at the spec, body, or both.

I think a general idiom should be: use them at both places as long as
is legal. Thus you provide the most information to the compiler and
future readers of the code.