Re: Ada Component Registry proposal

[sk <noname@myob.com>]

nolongersafeto@userealemailsniff.com:

 > I think this is not the right path. When Ada 2020 comes out and
 > we want to add a new subprogram to Ada05.Directory_Operations
 > does that mean we now have an Ada20.Directory_Operations that looks
 > the same but with the new procedure or do we add to it. No matter
 > what the answer is I don't think I like it.

The Ada83, Ada95, Ada0x scheme was intended to imply a "works-with"
relationship rather than a versioning relationship.

For example, there is a good chance that an Ada83.Directory_Operations
would resort to the subprogram'address methods for binding whereas
the Ada95.Directory_Operations would take advantage of the Interfaces.*
hierarchy and also possibly the subprogram'access capability of Ada'95.

I think the issue you describe tends to be a versioning issue rather
than a library-hierarchy issue and would occurr whether the root name
for the library was "root", "Ada95" or "CAL".

-- 
-------------------------------------------------
-- Merge vertically for real address
--
--     s n p @ t . o
--      k i e k c c m
-------------------------------------------------