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 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!news3.google.com!feeder.news-service.com!feeder.erje.net!nuzba.szn.dk!news.jacob-sparre.dk!pnx.dk!jacob-sparre.dk!ada-dk.org!.POSTED!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Derived private interface
Date: Wed, 6 Jul 2011 14:06:29 -0500
Organization: Jacob Sparre Andersen Research & Innovation
Message-ID: <iv2bnn$mg7$1@munin.nbi.dk>
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>
 <7c515c1d-d170-4cd2-8702-6532e09d6f42@y24g2000yqb.googlegroups.com>
NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net
X-Trace: munin.nbi.dk 1309979191 23047 69.95.181.76 (6 Jul 2011 19:06:31 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Wed, 6 Jul 2011 19:06:31 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6090
Xref: g2news1.google.com comp.lang.ada:20099
Date: 2011-07-06T14:06:29-05:00
List-Id: <comp.lang.ada>

"AdaMagica" <christ-usch.grein@t-online.de> wrote in message 
news:7c515c1d-d170-4cd2-8702-6532e09d6f42@y24g2000yqb.googlegroups.com...
>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.

Actually, it does. Indicators are not allowed on bodies unless those bodies 
can act as declarations.

> 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.

You can't do that in general (specifically, for protected subprograms) and 
that is intentional. The intent was that the indicators be provided only 
once (on the spec, or on a body acting as a spec). Beyond that, there was an 
allowance to put indicators on bodies when they were omitted from the spec; 
but there was never any intent that indicators would be *repeated* on 
bodies.

                                           Randy.