From: emery@MITRE-BEDFORD.ARPA (Emery)
Subject: re: renaming types
Date: Mon, 29-Jun-87 09:07:01 EDT [thread overview]
Date: Mon Jun 29 09:07:01 1987
Message-ID: <8706291307.AA02368@mitre-bedford.ARPA> (raw)
besides the two possible solutions (record with single component, and access),
there's a third possibility:
package A is
type T is private
private
type T is new B.BT;
end A;
However, this introduces all the 'overhead' of derived types. I've often wanted
to complete a private type definition as simply another type, so I think this
is a real problem, since several people (independently) have identified this
shortcoming (see the ACM SIGAda Language Issues WG discussions on this topic).
However, I'm not sure that 'rename' is the right operation. It seems to me
that 'subtype' may be even better:
package A is
type T is private;
private
subtype T is new B.BT; -- possibly constrained, too!
end A;
dave emery
emery@mitre-bedford.arpa
next reply other threads:[~1987-06-29 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1987-06-29 13:07 Emery [this message]
-- strict thread matches above, loose matches on Subject: below --
1987-06-29 13:24 renaming types Emery
[not found] <259745@QZCOM>
1987-06-28 0:08 ` "Johan Backlund FOA221"
1987-06-29 17:16 ` Robert Stockton
1987-06-26 17:28 "Art Evans"
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox