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=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.99.110.1 with SMTP id j1mr791400pgc.165.1504028556588;
        Tue, 29 Aug 2017 10:42:36 -0700 (PDT)
X-Received: by 10.36.111.206 with SMTP id x197mr123761itb.3.1504028556522;
 Tue, 29 Aug 2017 10:42:36 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.unit0.net!peer03.am4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!v29no1176459qtv.0!news-out.google.com!j49ni1558qtc.1!nntp.google.com!u11no1173703qtu.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 29 Aug 2017 10:42:36 -0700 (PDT)
In-Reply-To: <bc765307-02bd-4a38-b60c-4b743de6b3e4@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=2003:c7:83cd:c3eb:3c11:6af2:9f03:a765;
 posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf
NNTP-Posting-Host: 2003:c7:83cd:c3eb:3c11:6af2:9f03:a765
References: <bc765307-02bd-4a38-b60c-4b743de6b3e4@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <9055a948-fef5-4d84-b636-5a0b444ff8ea@googlegroups.com>
Subject: Re: procedure renames creates a primitive operation?
From: AdaMagica <christ-usch.grein@t-online.de>
Injection-Date: Tue, 29 Aug 2017 17:42:36 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 1746
X-Received-Body-CRC: 810897693
Xref: news.eternal-september.org comp.lang.ada:47834
Date: 2017-08-29T10:42:36-07:00
List-Id: <comp.lang.ada>

Hm, I'm not sure whether this is a compiler error (a nonprimitve becoming primitive by renaming?).

As a related example, the following renaming of a primitive op. creates a separate slot in the dispatching table, i.e. you can override both operations differently:

package Pack is

  type T is tagged private;

  procedure P (X: T);
  procedure Q (Y: T) renames P;

end Pack;

with Pack;
package Qack is

  type S is new Pack.T with private;

  overriding procedure P (X: S);
  overriding procedure Q (X: S);  -- no renaming of P!

end Qack;