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

Differences between 1.3 and version 1.4
Log of other versions for file ai12s/ai12-0401-1.txt

--- ai12s/ai12-0401-1.txt	2020/12/04 07:59:30	1.3
+++ ai12s/ai12-0401-1.txt	2020/12/11 22:22:26	1.4
@@ -1,8 +1,9 @@
-!standard 3.3(23.2/3)                                    20-10-29  AI12-0401-1/03
+!standard 3.3(23.2/3)                                    20-12-11  AI12-0401-1/04
 !standard 8.5.1(4.7/5)
 !standard 8.5.1(5/3)
 !class binding interpretation 20-10-15
 !status Amendment 1-2012 20-10-21
+!status ARG Approved 15-0-0  20-12-09
 !status work item 20-10-29
 !status ARG Approved 13-0-1  20-10-21
 !status work item 20-10-15
@@ -19,7 +20,7 @@
 
 We correct "known to be constrained" so that the nominal subtype of a
 qualified expression does not necessarily make a prefix "known to be
-constrained" even then the operand would not be "known to be constrained".
+constrained" even thought the operand would not be "known to be constrained".
 
 !question
 
@@ -42,10 +43,6 @@
 
 !wording
 
-[Editor's note: This wording is found in draft 27 of the RM, even though it is
-not yet approved. I had already added the wording when the additional issues 
-were detected, and I didn't want the RM to reflect known bad wording.]
-
 Modify 3.3(23.2/3)
   [to ensure known-to-be-constrained is not influenced by the nominal
    subtype of the qualified_expression]
@@ -113,13 +110,13 @@
 qualified (or converted) object is not itself "known to be constrained".
 That was always intended, but not captured by the rules.
 
-Both of these changes are incompatable with Ada 2012 as defined, but are
+Both of these changes are incompatible with Ada 2012 as defined, but are
 necessary to meet the design goal that a legal renaming cannot be of something
 that can be changed in a way that can cause erroneous execution.
 
 Note that we don't need to worry about generic formal in-out objects,
 even though they are effectively renames of the generic actual object,
-because a qualified_expression is a constant view, so would not be
+because a qualified_expression is a constant view, so it would not be
 permitted as the actual for a generic formal in-out object.
 
 !example
@@ -558,7 +555,7 @@
 put the rules closer to similar requirements and to avoid renumbering existing
 paragraphs.
 
-(2) "variable" isn't the only cases that cause problems. The "known to be
+(2) "variable" isn't the only case that causes problems. The "known to be
 constrained" rules encapulate those cases for composite types; for elementary
 types, it would be enough to require a constant other than a dereference of
 an access type (an access-to-constant can designate a variable).
@@ -570,8 +567,8 @@
 
 (4) The generic boilerplate should apply to these new rules. Rather than
 duplicating it, we make it apply to all of the Legality Rules in this 
-subclause. (The paragraph 4 and 4.1-4.3 rules probably don't need it, but it
-is harmless for them.)
+subclause. (The paragraph 4 and 4.1-4.3 rules probably don't need the
+boilerplate, but it is harmless for them.)
 
 We have reopened the AI to allow the ARG to review the updated wording.
 

Questions? Ask the ACAA Technical Agent