CVS difference for arm/source/07.mss

Differences between 1.107 and version 1.108
Log of other versions for file arm/source/07.mss

--- arm/source/07.mss	2010/11/25 03:11:50	1.107
+++ arm/source/07.mss	2011/02/05 09:14:58	1.108
@@ -1,10 +1,10 @@
 @Part(07, Root="ada.mss")
-@Comment{$Date: 2010/11/25 03:11:50 $}
+@Comment{$Date: 2011/02/05 09:14:58 $}
 @Comment{$Source: e:\\cvsroot/ARM/Source/07.mss,v $}
-@Comment{$Revision: 1.107 $}
+@Comment{$Revision: 1.108 $}
@@ -1910,7 +1910,12 @@
 @Chg{Version=[2],New=[the @nt{expression} of a return statement (see
 @RefSecNum{Return Statements})],Old=[]}
+@Chg{Version=[3],New=[the @nt{expression} of an
+@nt{expression_function_declaration} (see @RefSecNum{Expression Functions})],Old=[]}
+@ChgRef{Version=[3],Kind=[RevisedAdded]}@ChgNote{Only because the paragraph number has changed}
 @Chg{Version=[2],New=[the @nt{default_expression} or actual parameter for a
 formal object of mode @b{in} (see @RefSecNum{Formal Objects})],Old=[]}
@@ -2290,6 +2295,10 @@
+  @ChgAdded{Version=[3],Text=[Added wording so that expression functions can
+  return limited entities.]}
+  @ChgRef{Version=[3],Kind=[AddedNormal],ARef=[AI05-0178-1]}
   @ChgAdded{Version=[3],Text=[@b<Correction:> Added incomplete views
   to the list of reasons for a view of a type to be limited. This is not
   a change as the definition already was in
@@ -2725,6 +2734,20 @@
   we want to minimize disruption to Ada 95 implementations and users.]}
+  @ChgRef{Version=[3],Kind=[AddedNormal],ARef=[AI05-0232-1]}
+  @ChgAdded{Version=[3],Text=[This is a dynamic property and is determined by
+  the specific type of the parts of the actual object. In particular, if a part
+  has a class-wide type, the tag of the object might need to be examined in
+  order to determine if build-in-place is required. However, we expect that most
+  Ada implementations will determine this property at compile-time using some
+  assume-the-worst algorithm in order to chose the appropriate method to
+  implement a given call or aggregate. In addition, there is no attribute or
+  other method for a program to determine if a particular object has this
+  property (or not), so there is no value to a more careful description of this
+  rule.]}
   @ChgAdded{Version=[3],Text=[In the case of an @nt{aggregate}, if the full type
   of any part of the newly-created object is controlled, the anonymous object is
@@ -3418,12 +3441,13 @@
 and it will be finalized then.]
 The order in which the finalization of a master performs finalization of
 objects is as follows:
 Objects created by declarations in the master are finalized
 in the reverse order of their creation.
-For objects that were created
-by @nt{allocator}s for an access type whose
+For objects that were created by @nt{allocator}s for
+@Chg{Version=[3],New=[a named],Old=[an]} access type whose
 ultimate ancestor is declared in the master,
 this rule is applied as though each
 such object that still exists had been created
@@ -3433,7 +3457,10 @@
 of the ultimate ancestor type@Chg{Version=[2],New=[; the finalization of
 these objects is called the @i<finalization of the
 collection>@Defn{finalization of the collection}@Defn2{Term=[collection],
-Sec=[finalization of]}],Old=[]}.@Chg{Version=[2],
+Sec=[finalization of]}],Old=[]}.@Chg{Version=[3],New=[ Objects created by
+allocators for an anonymous access type that are not coextensions of some other
+object, are finalized in an arbitrary order during the finalization of their
+associated master.],Old=[]}@Chg{Version=[2],
 New=[ After the finalization of a master is complete, the objects finalized
 as part of its finalization cease to @i<exist>, as do any types and subtypes
 defined and created within the master.@PDefn2{Term=[exist],Sec=[cease to]}
@@ -4092,6 +4119,16 @@
   the same time as the outer object. (This was intended for Ada 95, but since
   the concept did not have a name, it was overlooked.)]}
+  @ChgRef{Version=[3],Kind=[Added],ARef=[AI05-0051-1]}
+  @ChgAdded{Version=[3],Text=[@Defn{inconsistencies with Ada 2005}@b<Correction:>
+  Allowed more flexibility as to when objects allocated from anonymous access
+  types are finalized. This could be inconsistent if objects are finalized in
+  a different order and that order caused different program behavior; however
+  programs that depend on the order of finalization within a single master are
+  already fragile and hopefully are rare.]}

Questions? Ask the ACAA Technical Agent