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

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

--- ai12s/ai12-0211-1.txt	2016/12/28 04:20:40	1.2
+++ ai12s/ai12-0211-1.txt	2017/07/18 23:19:26	1.3
@@ -1,4 +1,4 @@
-!standard 13.1.1(18.3/5)                                   16-12-20  AI12-0211-1/01
+!standard 13.1.1(18.3/5)                                   17-06-17  AI12-0211-1/02
 !standard 13.1.1(18.4/4)
 !class binding interpretation 16-12-20
 !status work item 16-12-20
@@ -48,31 +48,39 @@
 
 !wording
 
-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.{ In the case of an aspect whose
-value is a static expression, the specified expression shall match the
-inherited aspect by having the same value.}
-
-[Editor's note: we use "match" in the new wording and in the existing
-13.1.1(18.4/4), but we never say what it means for a static-valued aspect.
-We really ought to say what it means for an expression-valued aspect
-(full conformance), too, but we don't need that yet.]
-
-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 each ancestor shall match that 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(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.
 !discussion
 
 Obviously, one cannot have a type where a single aspect has two different

Questions? Ask the ACAA Technical Agent