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.236.125.6 with SMTP id y6mr2383503yhh.3.1398871391228; Wed, 30 Apr 2014 08:23:11 -0700 (PDT) X-Received: by 10.182.97.195 with SMTP id ec3mr21214obb.30.1398871390875; Wed, 30 Apr 2014 08:23:10 -0700 (PDT) Path: border2.nntp.dca3.giganews.com!backlog4.nntp.dca3.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!s7no129277qap.0!news-out.google.com!en3ni366igc.0!nntp.google.com!uq10no759271igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 30 Apr 2014 08:23:10 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=66.126.103.122; posting-account=KSa2aQoAAACOxnC0usBJYX8NE3x3a1Xq NNTP-Posting-Host: 66.126.103.122 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Are values of non-limited actual type for a limited formal type built in place? From: Adam Beneschan Injection-Date: Wed, 30 Apr 2014 15:23:11 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Original-Bytes: 2196 Xref: number.nntp.dca.giganews.com comp.lang.ada:186174 Date: 2014-04-30T08:23:10-07:00 List-Id: On Wednesday, April 30, 2014 8:07:05 AM UTC-7, Natasha Kerensikova wrote: >=20 > Is there anything in the RM about the build-in-place (or lack of > thereof) of value of limited formal type but non-limited actual type? The language rules about build-in-place refer to the "full type", so I woul= d assume that the non-limited actual type is what matters here, not the lim= ited formal type. RM 7.6(17.2/3). There's a similar situation that doesn't involve generics; it's possible fo= r a type to be declared as "limited private" in a package specification but= then be non-limited in the private part. (This allows the body of the pac= kage to use :=3D of the type, while preventing other packages from using th= e :=3D operator.) Here, since the rules refer to the "full type", build-in= -place is not required, even in other packages whose [partial] view of the = type is limited. -- Adam