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

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Sat, 31 Oct 2009 08:44:18 -0400, Stephen Leake wrote:

> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
>
>> Non-trivial it becomes when you have several such axes.
> 
> Yes. For example, Unbounded_Arrays have Index_Type and Item_Type.

Now consider I/O packages for Item_Type and Index_Type, and a package for
Unbounded_Array I/O that uses all these three. At some point the structure
of dependencies becomes a DAG.

>> Here is an example of a mesh of generic packages with 4 axes:
>>
>>    http://www.dmitry-kazakov.de/ada/fuzzy.htm#8
>>
>> Note that semantically the example is quite simple, almost evident. Its
>> implementation and use is horrific. I would never consider it "fixed".
> 
> Sorry, I don't see the complexity; what are the four axes?

Base number, enumeration of truth values, arrays of, map to the truth
value. These are initial parameters which group themselves in different
combinations to produce new types in generic instances of the second
generation of packages. These are selected in new combinations in the third
generation and so on.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de