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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,e92d558e5b77fce2
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII
Received: by 10.68.238.198 with SMTP id vm6mr11888697pbc.3.1328555477460;
        Mon, 06 Feb 2012 11:11:17 -0800 (PST)
Path: 
 lh20ni267787pbb.0!nntp.google.com!news1.google.com!postnews.google.com!d15g2000yqg.googlegroups.com!not-for-mail
From: Shark8 <onewingedshark@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Building limited types through nested creator functions
Date: Mon, 6 Feb 2012 11:11:17 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <1f36269b-78fa-4a8a-90c8-104c932e8658@d15g2000yqg.googlegroups.com>
References: 
 <40048c5a-ecf5-43e6-8c76-a294d0c333d1@l14g2000vbe.googlegroups.com>
NNTP-Posting-Host: 24.230.151.194
Mime-Version: 1.0
X-Trace: posting.google.com 1328555477 22208 127.0.0.1 (6 Feb 2012 19:11:17
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 6 Feb 2012 19:11:17 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: d15g2000yqg.googlegroups.com; posting-host=24.230.151.194;
 posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: HUALESNKRC
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1;
 rv:9.0.1) Gecko/20100101 Firefox/9.0.1,gzip(gfe)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2012-02-06T11:11:17-08:00
List-Id: <comp.lang.ada>

On Feb 5, 4:03=A0pm, Simon Belmont <sbelmont...@gmail.com> wrote:
> Hi,
>
> Consider two limited record types, inner and outer, with the former
> nested inside the latter. =A0If the records are public, then code can
> initialize the outer by specifying an aggregate for the inner, as in:
>
> type Inner is limited
> =A0 record
> =A0 =A0 e : Integer;
> =A0 end record;
>
> type Outer is limited
> =A0 record
> =A0 =A0 i : Inner;
> =A0 end record;
>
> o : Outer :=3D Outer'(i =3D> Inner'(e =3D> 42));
>
> However, if types are made private, suitable functions must be
> provided to make the appropriate objects. =A0If just Inner is private,
> then this can be done (assuming simple creator functions that just
> create the objects with the given values):
>
> o : Outer :=3D Outer'(i =3D> Make_Inner(arg =3D> 42));
>
> but if both are private, then the following:
>
> o : Outer :=3D Make_Outer (arg =3D> Make_Inner(arg =3D> 42));
>
> ends up being illegal, because in the code:
>
> function Make_Outer (arg : Inner) return Outer is
> begin
> =A0 return Outer'(i =3D> arg);
> end Make_Outer
>
> would end up trying to copy a limited type. =A0For the cases in which an
> existing object is passed in, this would be the appropriate action,
> but for cases where the object is built-in-place into the argument,
> clearly the intended behavior is to build it in place to the resultant
> object. =A0It's easy enough to use an access value, but as unnecessary
> use of access values is generally discouraged, I was just curious if
> there was an alternative mechanism to achieve the desired effect.
>
> -sb

Try this:

Function Make_Inner( I: Integer ) Return Inner is
begin
    Return Result : Inner:=3D Inner'( E =3D> I );
end Make_Inner;

Function Make_Outer( I: Integer ) Return Outer is
begin
    Return Result : Outer:=3D Outer'( I =3D> Make_Inner(I) );
end Make_Outer;

The 'trick' is to use all the parameters used in make_inner plus
whatever is needed in the Outer record for the parameter-list of
Make_Outer; thus you avoid all copying restrictions as you are really
building-in-place.