Re: Generic package parameters not externally visible : what's the rational ?

["Hibou57 (Yannick Duchêne)" <yannick_duchene@yahoo.fr>]

On 30 oct, 20:32, "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de>
wrote:
> Do you use generic in other generics?

While I do not know if it is the kind of reply you were expected, here
is mine : I use generics in other generics, when a generic has a
formal type parameter which come from another generic package. If want
want to assert the type T is provided (or derived from the one
provided) by a package P, then both P and T must appear in the
parameters. If P is generic (this can be legitimate), then you end up
with a generic using another generic.

Note : and in that case, this may be useful to make this package
visible from the outside (exporting the content via renames and
subtype, is not always done exhaustively)

You may also understand you can have generics dealing with generics,
when you use the Mixin pattern to add features in a well designed way,
to that if you ever modify the Mixin package, then modifications
applies to all the package created with this Minxin. The Mixin may be
generic, and the package it receives as a parameter as well.

Apologizes if this was not the kind of question you were requesting
about.