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=0.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!att!tsdiag!pedsga!petsd!joe
From: joe@petsd.UUCP (Joe Orost)
Newsgroups: comp.lang.ada
Subject: Re: Record rep specs for private components
Message-ID: <1635@petsd.UUCP>
Date: 20 Jun 89 13:06:12 GMT
References: <523@ajpo.sei.cmu.edu>
Reply-To: joe@petsd.UUCP (Joseph M. Orost)
Organization: Concurrent Computer Corporation, Tinton Falls, NJ
List-Id: <comp.lang.ada>

In article <523@ajpo.sei.cmu.edu> eberard@ajpo.UUCP writes:
>If type a.aa is private, then its underlying implementation should be
>unknown outside of package a. This means that it should be impossible
>for another program unit to specify how much space an instance of this
>type should take up. [Of course, package a could supply operations
>which could provide alternative representations of known sizes, and
>these could be used in other program units.]
>
>In short, if the rep spec is legal Ada, it should not be, and should
>be fixed in Ada 9X.

According to AI-00551/02 (DRAFT):

"If a component type is a private type, the size allowed in a component
clause for the type is determined by applying the above rules to the full
declaration of the private type."

I agree.

				regards,
				joe

--

 Full-Name:  Joseph M. Orost
 UUCP:       rutgers!petsd!joe
 ARPA:	     petsd!joe@RUTGERS.EDU, joe@PETSD.CCUR.COM
 Phone:      (201) 758-7284
 US Mail:    MS 322; Concurrent Computer Corporation; 106 Apple St
             Tinton Falls, NJ 07724