Re: How to declare a generic formal type "covered" by another?

[Natasha Kerensikova <lithiumcat@gmail.com>]

On 2014-05-01, J-P. Rosen <rosen@adalog.fr> wrote:
> Le 01/05/2014 09:33, Natasha Kerensikova a écrit :
>> The examples I had in mind are:
>>   - T is Stream_Element_Array, S is Stream_Element_Array (1 .. 4096)
> This is an unconstrained type and a constrained subtype of it.
>
>>   - T is Root_Stream_Type'Class, S is a concrete type derived from it
> This is an indefinite type, and a definite type derived from it.

So it seems they are indeed deeply different. Is there really no way to
describe both situations with the same words?

If I understand correctly your answer below, in both cases T is
indefinite while S is definite, right?

Also if infer correctly the vocabulary from 4.8(3/3), in both cases T
covers S, right?

If both are right, then the correct wording for my initial question
would be "How to declare a generic formal definite type covered by a
given format indefinite type?"

>>> 3) There is no way to say that S must be constrained, because being
>>> constrained is a matter of subtype, and only types matter for generics.
>> 
>> Well maybe the problem here is my limited vocabulary. I used the word
>> "constrained" there only to mean "Something := new S" or "Variable : S;"
>> are both valid, i.e. objects of that type can be created without
>> further information.
> This is definite vs. indefinite types.

OK, thanks

>> There must be some way to express that in generics.
> An unknown discriminant in a formal, i.e. "(<>)", expresses that the
> type may be indefinite.
>
> Now, thinking about it... When you derive a formal from an indefinite
> type, it stays indefinite. OTOH, you can derive from a definite type and
> give unknown discriminants to make indefinite. Add to that that a type
> is considered derived from itself, and the following compiles OK:
>
> procedure Essai is
>    [...]
> end Essai;
>
> Close enough to what you wanted?

Unfortunately not, since I need the covering indefinite type on a
shallower accessibility level than the covered definite type, since the
latter is only used to create reference to the former and those
references are used everywhere else.


Thanks for your help,
Natasha