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

--- ai12s/ai12-0388-1.txt	2020/08/22 04:40:12	1.1
+++ ai12s/ai12-0388-1.txt	2020/08/28 03:26:13	1.2
@@ -1,6 +1,7 @@
-!standard 4.3.5(0)                                       20-08-21  AI12-0388-1/01
+!standard 4.3.5(0)                                       20-08-27  AI12-0388-1/02
 !standard 6.1.1(26.10/4) 
 !standard 6.1.1(29/4)
+!standard 7.3.4(0)
 !standard D.4(16)
 !class presentation 20-08-21
 !status Amendment 1-2012 20-08-21
@@ -23,6 +24,8 @@
 (3) In 6.1.1(29/5), replace "previously" with "above as part of the Name 
 Resolution Rules for Post'Class".
 
+(4) In 7.3.4(3/5), add "each" to clarify.
+
 !question
 
 (1) Typically, there is a cross-reference "(see 13.1.1)" after each (forward)
@@ -35,6 +38,10 @@
 (3) In 6.1.1(29/5), "described previously" is pretty vague in a large 
 subclause. Should we be more specific? (Yes.)
 
+(4) In 7.3.4(3/5), one can read "a list of names preceded by an optional not"
+as meaning that there is a single not preceding the list, rather than a
+not for each name. Should this be clarified? (Yes.)
+
 !response
 
 (1) We typically put a cross-reference next to the first occurrence of any
@@ -50,6 +57,9 @@
 That's a bit long-winded, but it's much more specific than "previously",
 and the intended wording is a long ways away.
 
+(4) The intent is that "not" is allowed in front of each name individually,
+shown by 7.3.4(13-14/5).     
+
 !wording
 
 (1) Modify 4.3.5(12/5):
@@ -79,6 +89,13 @@
           cases the type of the attribute was described [previously]{above as
           part of the Name Resolution Rules for Post'Class}.
 
+(4) Modify 7.3.4(3/5):
+
+  A *type property aspect definition* is a list of names written in the syntax 
+  of a positional_array_aggregate. A subprogram property aspect definition is 
+  a list of names{, each optionally} preceded by {reserved word}[an optional]
+  /not/, also written in the syntax of a positional_array_aggregate.
+
 !discussion
 
 None.
@@ -122,6 +139,12 @@
    postcondition expression for a function with a controlling result or with a
    controlling access result; in those cases the type of the attribute was
    described above as part of the Name Resolution Rules for Post'Class.>
+
+
+!corrigendum 7.3.4(0)
+
+@dinsc
+See the conflict file for the changes.
 
 
 !corrigendum D.4(16)