From: stt@houdini.camb.inmet.com (Tucker Taft)
Subject: Re: Remote Types packages in distributed systems
Date: 1998/07/17
Date: 1998-07-17T00:00:00+00:00 [thread overview]
Message-ID: <Ew9DJo.LDF.0.-s@inmet.camb.inmet.com> (raw)
In-Reply-To: 6ooaao$f9d@top.mitre.org
Michael F Brenner (mfb@mbunix.mitre.org) wrote:
: There are two contradictory statements in Appendix E of the Ada
: Language Reference Manual pertaining to remote-types. Which one
: takes precedence?
: E.2(9) Remote Types. The declaration of the library unit can depend
: only on other remote types library units, or [a shared passive or a pure
: unit]; the body of the library unit is unrestricted; ...
: E.2.2(4) A remote types library unit is a library unit to which
: the pragma Remote_Types applies. The following restrictions
: apply to the declaration of such a library unit:
: it shall be preelaborable; ...
: It cannot have a preelaborable declaration if its body is unrestricted
: and can import a non-preelaborable unit.
Saying that the *spec* (aka "declaration") of a Remote_Types unit shall be
preelaborable says nothing about the preelaborability of its body
(aka "completion").
: Which of these two contradictory statements shall rule?
I don't see the contradiction.
: Mike Brenner
--
-Tucker Taft stt@inmet.com http://www.inmet.com/~stt/
Intermetrics, Inc. Burlington, MA USA
prev parent reply other threads:[~1998-07-17 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-17 0:00 Remote Types packages in distributed systems Michael F Brenner
1998-07-17 0:00 ` Tucker Taft [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox