CVS difference for ai12s/ai12-0373-1.txt

Differences between 1.7 and version 1.8
Log of other versions for file ai12s/ai12-0373-1.txt

--- ai12s/ai12-0373-1.txt	2020/04/28 02:33:21	1.7
+++ ai12s/ai12-0373-1.txt	2020/05/02 03:43:14	1.8
@@ -1,4 +1,4 @@
-!standard 3.1(1)                                     20-04-26  AI12-0373-1/05
+!standard 3.1(1)                                     20-04-29  AI12-0373-1/06
 !standard 4.2.1(3/5)
 !standard 4.2.1(4/5)
 !standard 4.2.1(5/5)
@@ -10,6 +10,7 @@
 !standard 13.14(3/5)
 !class Amendment 20-03-22
 !status Amendment 1-2012 20-03-22
+!status ARG Approved 14-0-0  20-04-29
 !status work item 20-03-22
 !status received 20-03-22
 !priority Low
@@ -17,9 +18,6 @@
 !subject Bunch 'o fixes
 !summary
 
-[Editor's note: These fixes, while unapproved, are included in the draft
-25 RM as they are not expected to be controversial.]
-
 A number of fixes to the draft Ada 202x Standard are needed:
 
 (1) The definition of statically names only excludes record components found
@@ -218,7 +216,7 @@
 (3) Clearly, objects are intended to be a subset of entities. There is
 plenty of wording that assumes that already in the Standard. For instance,
 8.5(3) renaming says that a renaming elaborates the name to determine the
-entity. Since we can rename array subcomponents, clearly it's expected that
+entity. Since we can rename an array subcomponent, clearly it's expected that
 they're entities.
 
 Moreover, 4.1(11/2) says:
@@ -228,9 +226,9 @@
 So an entity is effectively anything that can be denoted by a name. 
 
 However, 3.1(1) is the only definition of entities in the Standard. 
-We don't want to make it seem that a array component or type is not an 
-entity simply because it doesn't have a declaration with a name. So we improve
-the wording to make it clear there are other kinds of entities.
+We don't want to make it seem that an array component or an array type is not
+an entity simply because it doesn't have a declaration with a name. So we 
+improve the wording to make it clear there are other kinds of entities.
 
 (4) The equivalence of 4.2.1(7/5) ensures that no illegal call will be made.
 However, there is no reason to allow the definition of useless things, that
@@ -246,7 +244,7 @@
 modify the rules of 4.2 to make it clear how integer and real literals 
 resolve.
 
-(7) The usage of Bit_Order is clear that of a representation aspect, and the
+(7) The usage of Bit_Order is clearly that of a representation aspect, and the
 list of representation aspects in the AARM confirms it. Thus we add wording
 to clarify that Bit_Order is a representation aspect.
 
@@ -368,6 +366,19 @@
 end of the immediately enclosing declaration list, or in the
 case of the declaration of a library unit, at the end of the visible
 part of the entity.
+
+!corrigendum 13.1.1(18.6/4)
+!comment This was the original paragraph number, AI12-0211-1 changed it.
+!comment We have to use the original number here so that a conflict is 
+!comment properly detected.
+
+@drepl
+The Default_Iterator, Iterator_Element, Implicit_Dereference,
+Constant_Indexing, and Variable_Indexing aspects are nonoverridable.
+@dby
+The Default_Iterator, Iterator_Element, Implicit_Dereference,
+Constant_Indexing, Variable_Indexing, Aggregate, Max_Entry_Queue_Length, and 
+No_Controlled_Parts aspects are nonoverridable.
 
 !corrigendum 13.14(3/5)
 

Questions? Ask the ACAA Technical Agent