CVS difference for ai05s/ai05-0142-4.txt

Differences between 1.6 and version 1.7
Log of other versions for file ai05s/ai05-0142-4.txt

--- ai05s/ai05-0142-4.txt	2010/01/09 01:31:29	1.6
+++ ai05s/ai05-0142-4.txt	2010/04/17 04:50:16	1.7
@@ -1,4 +1,4 @@
-!standard 3.10(9/2)                                  09-12-09  AI05-0142-4/05
+!standard 3.10(9/2)                                  10-04-12  AI05-0142-4/06
 !standard 3.10.2(13.1/2)
 !standard 6.1(15/2)
 !standard 6.1(23)
@@ -153,7 +153,7 @@
 different than that enclosing the call. The only place all of those conditions exist is
 in the initializer of an allocator; in all other cases this check will always pass.
 
-Add a new Dynamic Semantics after 6.4.1(15): (this would be a new, outer level, bullet)
+Add a new Dynamic Semantics rule after 6.4.1(15): (this would be a new, outer level, bullet)
 
 In a function call, for each explicitly aliased parameter, a
 check is made that the accessibility level of the master of the actual object is
@@ -201,6 +201,17 @@
 check on explicitly aliased parameters will necessarily fail if any such anonymous objects
 exist. This is necessary to avoid requiring the objects to live as long as the access type or
 the implementation complexity of an implicit coextension.
+
+Modify the first sentence of C.6(12):
+
+If an atomic object is passed as a parameter, then the [type of the] formal parameter shall
+either [be atomic]{have an atomic type} or allow pass by copy [(that is, not be a nonatomic
+by-reference type)]. 
+
+AARM Reason: A formal parameter allows pass by copy if it is not aliased and it is of a type
+that allows pass by copy (that is, is not a by-reference type).
+
+[Editor's note: We're deleting the parenthetical remark, as it is no longer true by itself.]
 
 
 (Note: The following requires AI05-0143-1 to be approved.)

Questions? Ask the ACAA Technical Agent