From: AdaMagica <christ-usch.grein@t-online.de>
Subject: Re: procedure renames creates a primitive operation?
Date: Tue, 29 Aug 2017 10:42:36 -0700 (PDT)
Date: 2017-08-29T10:42:36-07:00 [thread overview]
Message-ID: <9055a948-fef5-4d84-b636-5a0b444ff8ea@googlegroups.com> (raw)
In-Reply-To: <bc765307-02bd-4a38-b60c-4b743de6b3e4@googlegroups.com>
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;
next prev parent reply other threads:[~2017-08-29 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 15:39 procedure renames creates a primitive operation? Jere
2017-08-29 17:42 ` AdaMagica [this message]
2017-08-31 1:24 ` Randy Brukardt
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox