From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,fb904ed5b1bd56bb
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1995-03-21 14:19:20 PST
Newsgroups: comp.lang.ada
Path: 
 nntp.gmd.de!dearn!blekul11!ccsdec1.ufsia.ac.be!reks.uia.ac.be!idefix.CS.kuleuven.ac.be!
 Belgium.EU.net!EU.net!howland.reston.ans.net!gatech!news-feed-1.peachnet.edu!paperboy.wellfleet.com!noc.near.net!inmet!spock!stt
From: stt@spock.camb.inmet.com (Tucker Taft)
Subject: Re: Differences between RM 5.0 and 6.0
Message-ID: <D5syBG.M2A@inmet.camb.inmet.com>
Sender: news@inmet.camb.inmet.com
Organization: Intermetrics, Inc.
X-Newsreader: TIN [version 1.1 PL8]
References: <Mats.Weber-2003952132250001@mlma11.matrix.ch>
Date: Tue, 21 Mar 1995 18:06:51 GMT
Date: 1995-03-21T18:06:51+00:00
List-Id: <comp.lang.ada>

Mats Weber (Mats.Weber@matrix.ch) wrote:

: I have a paper copy of version 5.0 of the Ada 95 RM. Can I use it safely
: or are there many changes from 5.0 to 6.0 (the standard) ?

The major changes from 5.0 to 6.0 were:

   1) Children of generics changed significantly -- "with"ing a child
      of a parent generic package makes a nested generic of the same name
      visible within any instance of the parent generic;

   2) The rules for static expressions were rewritten for clarity;
      the concept of "potentially static" was dropped;

   3) The accessibility rules were rewritten for clarity, using the
      hopefully more intuitive concept of accessibility "levels";

   4) Preinstantiations of the numeric text I/O packages were
      added for the predefined numeric types;

   5) Formal derived types may no longer have an explicit "known"
      discriminant_part; they may only have an unknown discriminant_part
      "(<>)" or inherit discriminants from the specified ancestor type;

   6) Incomplete types may be used as formal parameter types in the
      definition of the designated profile for an access-to-subprogram type
      (this allows a record to contain a pointer to a subprogram that
      takes that same record type as a parameter);

   7) Remote access types may now be declared in remote types packages
      (they used to only be allowed in remote call interface packages).

-Tucker Taft  stt@inmet.com