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

--- ai12s/ai12-0377-1.txt	2020/09/12 02:56:35	1.10
+++ ai12s/ai12-0377-1.txt	2021/05/30 00:35:11	1.11
@@ -67,11 +67,11 @@
 If the mode is out, the actual parameter is a view conversion, and the type of
 the formal parameter is a scalar type, then either:
 
-  * the target and operand type both do not have the Default_Value aspect
+  * neither the target type nor the operand type has the Default_Value aspect
     specified; or
 
-  * the target and operand type both have the Default_Value aspect
-    specified, and there shall exist a type (other than a root numeric
+  * both the target type and the operand type shall have the Default_Value
+    aspect specified, and there shall exist a type (other than a root numeric
     type) that is an ancestor of both the target type and the operand type.
 
 [Editor's note: This removes the access part of this rule, and makes a
@@ -135,8 +135,8 @@
 @xbullet<there shall exist a type (other than a root numeric type) that is
 an ancestor of both the target type and the operand type; and>
 @dby
-@xbullet<the target and operand type both do not have the Default_Value aspect
-specified; or>
+@xbullet<neither the target type nor the operand type has the Default_Value
+aspect specified; or>
 
 !corrigendum 6.4.1(5.3/4)
 
@@ -144,8 +144,8 @@
 @xbullet<in the case of a scalar type, the type of the operand of the
 conversion shall have the Default_Value aspect specified.>
 @dby
-@xbullet<the target and operand type both have the Default_Value aspect
-specified, and there shall exist a type (other than a root numeric
+@xbullet<both the target type and the operand type shall have the Default_Value
+aspect specified, and there shall exist a type (other than a root numeric
 type) that is an ancestor of both the target type and the operand type.>
 
 !corrigendum 6.4.1(13.1/4)
@@ -908,3 +908,31 @@
 
 ****************************************************************
 
+From the WG 9 review, issue #6 [Randy Brukardt]
+
+6.4.1(5.2/5) reads:
+
+    the target and operand type both do not have the Default_Value aspect
+    specified; or
+
+"Type" seems wrong, as there are two types here, so why the singular?
+
+There is similar text in 6.4.1(5.3/5).
+
+Suggested fix:
+
+Tucker Taft suggested replacing the 6.4.1(5.2/5), as the combination of
+"both" and "not" is confusing, with:
+
+    neither the target type nor the operand type has the Default_Value aspect
+    specified;
+
+John Barnes suggested moving the "both", and I had noted that the end of
+6.4.1(5.3/5) repeats "type", so that gives for 6.4.1(5.3/5):
+
+    both the target type and the operand type shall have the Default_Value
+    aspect specified, and there shall exist a type (other than a root numeric
+    type) that is an ancestor of both the target type and the operand type.
+
+[Editor's note: This was processed as an Editorial Review on AI12-0377-1.]
+****************************************************************