CVS difference for ai05s/ai05-0253-1.txt

Differences between 1.2 and version 1.3
Log of other versions for file ai05s/ai05-0253-1.txt

--- ai05s/ai05-0253-1.txt	2011/06/20 04:55:19	1.2
+++ ai05s/ai05-0253-1.txt	2011/07/29 01:12:41	1.3
@@ -1,5 +1,7 @@
-!standard 3.10.2(13.2/3)                             11-06-16    AI05-0253-1/01
+!standard 3.10.2(14/3)                             11-07-28    AI05-0253-1/02
 !class Amendment 11-06-16
+!status Amendment 2012 11-07-28
+!status ARG Approved 10-0-2  11-06-25
 !status work item 11-06-16
 !status received 11-05-13
 !priority Low
@@ -7,7 +9,8 @@
 !subject Accessibility of allocators for anonymous access of an object
 !summary
 
-**TBD.
+The accessibility level of an allocator assigned to a stand-alone object of an
+anonymous access type is that of the stand-alone object.
 
 !question
 
@@ -36,14 +39,45 @@
 
 !wording
 
-** TBD.
+Insert immediately prior to the last sentence of 3.10.2 (14/3):
 
+For an anonymous allocator whose type is that of a stand-alone object of
+an anonymous access-to-object type, the accessibility level is that of the
+declaration of the stand-alone object.
+
 !discussion
 
+Obviously, this needs to be defined, and the level of the declaration is the
+only reasonable choice.
+
+!corrigendum 3.10.2(14/2)
 
-!ACATS test
+@drepl
+@xbullet<The accessibility level of an object created by an @fa<allocator> is
+the same as that of the access type, except for an @fa<allocator> of an
+anonymous access type that defines the value of an access parameter or
+an access discriminant. For an @fa<allocator> defining the value of
+an access parameter, the accessibility level is that of the
+innermost master of the call. For one defining an access
+discriminant, the accessibility level is determined as follows:>
+@dby
+@xbullet<The accessibility level of an object created by an @fa<allocator> is
+the same as that of the access type, except for an @fa<allocator> of an
+anonymous access type (an @i<anonymous allocator>) in certain
+contexts, as follows: For an anonymous allocator
+that defines the result of a function with an access result, the
+accessibility level is determined as though the @fa<allocator> were in
+place of the call of the function; in the special case of a call
+that is the operand of a type conversion, the level is that of the
+target access type of the conversion. For an anonymous allocator
+defining the value of an access parameter, the accessibility level is
+that of the innermost master of the call.
+For an anonymous allocator whose type is that of a stand-alone object of
+an anonymous access-to-object type, the accessibility level is that of the
+declaration of the stand-alone object. For one defining an access
+discriminant, the accessibility level is determined as follows:>!ACATS test
 
-** TBD.
+Create an ACATS C-Test to test this case.
 
 !appendix
 
@@ -78,6 +112,26 @@
 
 Yes, I agree the level of an anonymous allocator in this context should remain
 local.
+
+****************************************************************
+
+From: Gary Dismukes
+Sent: Saturday, June 25, 2011  9:31 AM
+
+Proposed wording for AI05-0253-1 (accessibility of anonymous allocators)
+
+!summary
+
+The accessibility level of an allocator assigned to a stand-alone object
+of an anonymous access type is that of the stand-alone object.
+
+!wording
+
+Insert immediately prior to the last sentence of 3.10.2 (14/3):
+
+For an anonymous allocator whose type is that of a stand-alone object of
+an anonymous access-to-object type, the accessibility level is that of the
+stand-alone object.
 
 ****************************************************************
 

Questions? Ask the ACAA Technical Agent