CVS difference for ais/ai-00330.txt

Differences between 1.1 and version 1.2
Log of other versions for file ais/ai-00330.txt

--- ais/ai-00330.txt	2003/07/26 03:26:02	1.1
+++ ais/ai-00330.txt	2004/12/09 19:55:30	1.2
@@ -1,5 +1,7 @@
-!standard  4.6      (05)                              03-07-22  AI95-00330/01
+!standard  4.6      (05)                              04-12-03  AI95-00330/02
 !class binding interpretation 03-07-22
+!status Amendment 200Y 04-12-03
+!status ARG Approved 9-0-1  04-11-21
 !status work item 03-07-22
 !status received 03-04-16
 !priority Low
@@ -30,20 +32,16 @@
 The standard often does say "actual parameter" to mean "generic actual
 parameter". For examples, see 12.4(7) and 12.7(5).
-This ambiguity makes me wonder whether an untagged type conversion is
-officially considered to be a view conversion when it occurs as a
-"generic actual parameter" of a generic instantiation. I hope not.
 If a generic actual parameter of mode in out would qualify as a view
 conversion, then the legality of an object name used as a generic actual
 parameter would differ from that used in an object renaming declaration.
 Thus we confirm the behavior of the ACATS tests and tighten the wording
-of 4.6(5).
+of 4.6(5) to apply only in calls (and not instantiations or names).
-Change 4.6(5) to add "non-generic" in front of "actual parameter".
+Change 4.6(5) to add "in a call" in front of "as an actual parameter".
 !corrigendum  4.06(05)
@@ -55,7 +53,7 @@
 A @fa<type_conversion> whose operand is the @fa<name> of an object is called a
 @i<view conversion> if both its target type and operand type are tagged, or if
-it appears as a non-generic actual parameter of mode @b<out> or @b<in out>;
+it appears as or if it appears in a call as an actual parameter of mode @b<out> or @b<in out>;
 other @fa<type_conversion>s are called @i<value conversions>.
 !ACATS test

Questions? Ask the ACAA Technical Agent