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

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

--- ai12s/ai12-0211-1.txt	2017/07/18 23:19:26	1.3
+++ ai12s/ai12-0211-1.txt	2017/10/12 02:22:39	1.4
@@ -1,4 +1,4 @@
-!standard 13.1.1(18.3/5)                                   17-06-17  AI12-0211-1/02
+!standard 13.1.1(18.3/5)                           17-10-11  AI12-0211-1/03
 !standard 13.1.1(18.4/4)
 !class binding interpretation 16-12-20
 !status work item 16-12-20
@@ -48,39 +48,25 @@
 
 !wording
 
-Modify 13.1(18.2/3):
-
-An aspect_specification or representation item that specifies a
-representation aspect that would have been chosen in the absence of the
-aspect_specification or representation item is said to be confirming.
-{In the case of an aspect whose value is a name, this means that, the
-specified name shall be the same as the inherited aspect and therefore
-denote the same declarations as would the inherited name. In the case of
-an aspect whose value is a static expression, the specified expression
-shall have the same static value as the inherited aspect.}  The aspect
-value specified in this case is said to be a confirming representation
-aspect value. Other values of the aspect are said to be nonconfirming,
-as are the aspect_specifications and representation items that specified
-them.
-
-Modify 13.1.1(18.3/5): [As modified by AI12-0206-1]
-
-If a nonoverridable aspect is directly specified for a type T, then any
-explicit specification of that aspect for any other descendant of T
-shall be *confirming*. [In the case of an aspect whose value is a name,
-this means that, the specified name shall match the
-inherited aspect and therefore denote the same declarations as would the
-inherited name.]
-
-Add after 13.1.1(18.4/4):
-
-If a type inherits a nonoverridable aspect from multiple ancestors, the
-value of the aspect inherited from any given ancestor shall be
-confirming for those of the other ancestors.
-
-AARM Reason: If more than one progenitor of a type T specifies a
-nonoverridable aspect, they all have to specify the same primitive of T.
-Otherwise, we'd have two different values for the aspect.
+Modify 13.1.1(18.3/5): [As modified by AI12-0206-1]
+
+  If a nonoverridable aspect is directly specified for a type T, then
+  any explicit specification of that aspect for any [other] descendant
+  of T {(other than T itself)} shall be *confirming*. In the case of an
+  aspect whose value is a name, this means that the specified name shall
+  {*}match{*} the inherited aspect [and therefore] {in the sense that it
+  shall} denote the same declarations as would the inherited name.
+
+Add after 13.1.1(18.4/4):
+
+  If a type inherits a nonoverridable aspect from multiple ancestors,
+  the value of the aspect inherited from any given ancestor shall be
+  confirming of the values inherited from all other ancestors.
+
+    AARM Reason: If more than one progenitor of a type T specifies a
+    nonoverridable aspect, they all have to specify the same primitive
+    of T. Otherwise, we'd have two different values for the aspect.
+
 !discussion
 
 Obviously, one cannot have a type where a single aspect has two different
@@ -140,5 +126,13 @@
 Sent: Sunday, October 2, 2016  7:07 PM
 
 Agreed with your suggestion of making such a situation illegal.
+
+****************************************************************
+
+From: Tucker Taft
+Sent: Wednesday, October 11, 2017  4:44 PM
+
+Here is a modest update to AI12-0211, to try to untangle some of the wording
+of the first attempt. [This is version /03 - Editor.]
 
 ****************************************************************

Questions? Ask the ACAA Technical Agent