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

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

--- ai05s/ai05-0164-1.txt	2009/10/23 06:06:31	1.2
+++ ai05s/ai05-0164-1.txt	2009/12/01 18:56:56	1.3
@@ -1,12 +1,14 @@
-!standard 3.4(18/2)                                   09-10-21  AI05-0164-1/01
+!standard 3.4(18/2)                                   09-11-30  AI05-0164-1/02
 !standard 6.1(27.1/2)
+!standard 6.1(28.2/2)
 !class binding interpretation 09-10-21
+!status ARG Approved 10-0-1  09-11-08
 !status work item 09-10-21
 !status received 09-06-23
 !priority Low
 !difficulty Medium
 !qualifier Omission
-!subject Parameters of Access-to-subprogram parameters and derivation
+!subject Parameters of access-to-subprogram parameters and derivation
 !summary
 
 The types of parameters of access-to-subprogram parameters are not modified
@@ -69,7 +71,7 @@
 The profile of an inherited subprogram (including an inherited enumeration literal)
 is obtained from the profile of the corresponding (user-defined) primitive subprogram
 of the parent or progenitor type, after systematic replacement of each subtype of its
-profile (see 6.1) {other than those found in any access parameters of an access-to-subprogram type}
+profile (see 6.1){, other than those found in the designated profile of an access_definition,}
 that is of the parent or progenitor type with a *corresponding subtype* of the derived type.
 For a given subtype of the parent or progenitor type, the corresponding subtype of the derived
 type is defined as follows: 
@@ -80,6 +82,11 @@
 * For any access parameters of an access-to-subprogram type, the subtypes of
   the {designated} profile of the parameter type.
 
+Modify 6.1(28.2/2):
+
+* For any access result type of an access-to-subprogram type, the subtypes of
+  the {designated} profile of the result type.
+
 !discussion
 
 Changing the definition of the profile of a subprogram is not possible; it's
@@ -91,8 +98,8 @@
 
 ---
 
-The change to 6.1(27.1/2) is needed as access-to-subprogram types have designated
-profiles, but don't directly have a profile.
+The changes to 6.1(27.1/2) and 6.1(28.2/2) are needed as access-to-subprogram types have
+designated profiles, but don't directly have a profile.
 
 
 !corrigendum 3.4(18/2)
@@ -108,7 +115,7 @@
 The profile of an inherited subprogram (including an inherited enumeration literal)
 is obtained from the profile of the corresponding (user-defined) primitive subprogram
 of the parent or progenitor type, after systematic replacement of each subtype of its
-profile (see 6.1) other than those found in any access parameters of an access-to-subprogram type
+profile (see 6.1), other than those found in the designated profile of an @fa<access_definition>,
 that is of the parent or progenitor type with a @i<corresponding subtype> of the derived type.
 For a given subtype of the parent or progenitor type, the corresponding subtype of the derived
 type is defined as follows: 
@@ -122,6 +129,15 @@
 @dby
 @xbullet<For any access parameters of an access-to-subprogram type, the subtypes of
 the designated profile of the parameter type.>
+
+!corrigendum 6.1(28.2/2)
+
+@drepl
+@xbullet<For any access result type of an access-to-subprogram type, the subtypes of
+the profile of the result type.>
+@dby
+@xbullet<For any access result type of an access-to-subprogram type, the subtypes of
+the designated profile of the result type.>
 
 !ACATS Test
 

Questions? Ask the ACAA Technical Agent