CVS difference for ais/ai-00229.txt

Differences between 1.14 and version 1.15
Log of other versions for file ais/ai-00229.txt

--- ais/ai-00229.txt	2002/03/13 00:48:27	1.14
+++ ais/ai-00229.txt	2002/05/25 03:42:18	1.15
@@ -1,8 +1,9 @@
-!standard  3.10.2   (32)                             01-10-17  AI95-00229/04
+!standard  3.10.2   (32)                             02-05-14  AI95-00229/05
 !class binding interpretation 00-04-10
-!status ARG approved 7-0-2  01-10-07
+!status Amendment 200Y 02-05-14
+!status ARG Approved 7-0-2  01-10-07
 !status work item 01-06-12
-!status ARG approved 6-0-2  01-05-20
+!status ARG Approved 6-0-2  01-05-20
 !status work item 01-05-04
 !status received 00-04-10
 !priority Medium
@@ -12,15 +13,15 @@
 
 !summary
 
-The expression P'Access (where P denotes a subprogram declared in a generic) is
-illegal within a generic body (or the body of a child unit of the generic) if
-the ultimate ancestor of the expected access type is a generic formal type or
-is not declared within the generic unit.
+The expression P'Access (where P denotes a subprogram declared in a generic
+unit) is illegal within the generic body (or the body of a child unit of the
+generic) if the ultimate ancestor of the expected access type is a generic
+formal type or is not declared within the generic unit.
 
 !question
 
 The following piece of code seems to show a case where the accessibility rules
-allow the creation of reference to a subprogram that doesn't exist anymore.
+allow the creation of a reference to a subprogram that doesn't exist anymore.
 
 This case doesn't seem to be caught by the "assume the worst" rule in the last
 sentence of RM95 3.10.2(32), because Foo is not declared in a generic body.

Questions? Ask the ACAA Technical Agent