Re: Usage of Interfaces with Ada 95

[Michael Erdmann <Michael.Erdmann@snafu.de>]

Matthew Heaney wrote:

> Hyman Rosen <hyrosen@mail.com> writes:
> 
>> Using inheritance for iterators is silly and wrong, since the base
>> iterator class can't express anything about what it iterates over, or
>> what type it returns.
>> 
>> Go see the Charles library for how to do it right.
> 
> Amen to that.  He needs a generic algorithm, but just doesn't know how
> to express it in Ada.  Use the Source, Luke!
> 
> <http://home.earthlink.net/~matthewjheaney/charles/>
This is not the point! The point is, that i like to setup a 
repository of concepts, which is specialized when it is used.
For example, the iterator (or enumerator) is a very general
concept which requieres basicaly the following methods

    First          - Return the first element
    Next           - Fetch the next element
    HasMoreElement - Check if there is more


By introducing a set of concepts i like to standarize the 
conding. For example the arugment between two developers already
start with naming of the method HasMoreElements. In order to avoid 
such discussions i like to introduce interface class as for example 
in java. 
The nice thing about java interfaces is that all classes
are derived from the Object class. This is not the case in Ada,
there i dont have such a thing as the Object class. And it seems
that i need use generics making the handling a little bit 
complicated because:

   1. Define a generic package with your abstract interface
      which has a type as argument.
   2. Specialize the interface for the requiered type,
      which is still abstract.
   3. Implement classes around the specialzed types.

I am looking for a way of avoiding step 1.