Re: limited /non-limited tagged type

[Georg Bauhaus <rm-host.bauhaus@maps.futureapps.de>]

On 3/4/11 11:40 PM, Hacid wrote:

>> private generic
>>      type Element is new Object with private;
>> package Foo_3.Pools is
>>
>> Foo_3.Copy can then effectively be called from within
>> Foo_3.Pools.Copy.
>
>
> I have no compilation error on my file foo_3-pools.adb.
> But this construction make only a partial copy of the derivated
> element.
> And I would want a full one. That was what I tried to explain...but I
> am not very understandable in English :o)

I should wait until you have answered Adam's comments.

Nevertheless, an important distinction might be whether

- Element is your derived type

- Someone else's

In the first case, it is all your Copy operation having access
to all fields of Element.

If Element is all yours, then I don't see how proper nesting
of your Copy procedures might miss a component:

Premises IIUC
===
- The publicly limited objects live in arrays,

- It will be OK to overwrite all object data privately,
per object, as long as the data is written by your own
Copy procedure, and not by someone else's.

Then your private Copy procedures could invoke any parent's
private Copy procedure (assuming all Copy procedures in the
derivation hierarchy can be called by yours).  This will
copy all record components of the parent's view of the object.
When the parent's copy is done, Copy copies the remaining
components.