Re: making a son benefit access ton an instanciation of a generic package required as a formal parameter to his father and instanciated by him

[Mehdi Saada <00120260a@gmail.com>]

Le lundi 22 janvier 2018 16:36:10 UTC+1, Mehdi Saada a écrit :
> > Imagine this:
> > generic
> >    package P1 is new GP1 (<>);
> >    package P2 is new GP1 (<>);
> > package GP2 is... end GP2;
> package Inst1 is new GP1;
> package Inst2 is new GP2 (Inst1, Inst1);
> then you would end up with two different handlers for the same exception (since formals P1 and P2 are actually the same package Inst1). And that's a no-no!
Ah ! Now I get it. Earlier explanations seemed like chinese homonyms, but a fine example makes it crystal clear. The terminology is this area, is still too abstract and confuses me, 'cause I barely touched it yet. I didn't considered that eventuality of two different views (is that the term ?) of the same instances screwing with each others... eventhough it's not so much convoluted.


... Thinking about it, I was under the false assumption that the generic itself was passed as parameter, and instanciated by or inside the second generic package, whereas it's clear from the instanciation of the latter, that it takes on an INSTANCE. I wasn't even conscious of that confusion. It just messed up my reasoning...