Re: Ada83 equivalents for Ada95

[JP Thornley <jpt@diphi.demon.co.uk>]

In article: <31A66DAA.7418@sud.ed.ray.com>  Joe Gwinn 
<gwinn@sud.ed.ray.com> writes:
> 
> We have the Ada83 versus Ada95 problem as well.  In short, we plan to 
> use the Ada83 subset of Ada95, so that in some future, we will be able 
> to transition to Ada95, should the customer so desire. 
> [snip]

We are in the same position - but with (almost) total upward 
compatibility it isn't too difficult.

On a different but related topic, has anyone looked at designing Ada 83 
code so that the transition to using the *new* features of Ada 95 is as 
easy as possible.  For example, I can't use child packages in Ada 83, 
but perhaps I can make greater use of sub-packages, so that when the 
switch is made I can easily pull out the children and get the benefit in 
subsequent development (although I'm not sure about how much I would be 
forced to change the 'with's).

Similar ideas for tagged types, protected objects, .... would be very 
valuable for those of us who aren't going to be using Ada 95 for a few 
years yet.

[This may have been asked before, but I missed any replies (if there 
were any).]

Phil Thornley

-- 
------------------------------------------------------------------------
| JP Thornley    EMail jpt@diphi.demon.co.uk                           |
------------------------------------------------------------------------