Re: limited agregate and limited components default initialization

["Robert I. Eachus" <rieachus@comcast.net>]

On 4/1/2018 7:36 PM, Jean-Claude Rostaing wrote:
> Ok, now I know why what I wanted to do was impossible. To store an object into an accessor or whatever, or to create it with allocator, with only a given "value" of this limited type, you need to COPY this value, whatever you do. Which goes against the very idea of limited type.
> I feel more intelligent thanks to that...
> 
There is a messy but workable solution.  Create (in the private part or 
package body) a non-limited type which has all the non-limited stuff 
from your limited type.   Call it Foo.  Now you can create an object of 
type Foo initialize it however you want, and then create the limited 
object with an aggregate containing Foo.

Why messy? You have to add .Foo all over the place.  But it works.  (Of 
course if there are unconstrained limited components, you may be hosed.)