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

Differences between 1.4 and version 1.5
Log of other versions for file ai05s/ai05-0013-1.txt

--- ai05s/ai05-0013-1.txt	2006/12/16 03:13:17	1.4
+++ ai05s/ai05-0013-1.txt	2007/05/26 01:43:59	1.5
@@ -1,4 +1,4 @@
-!standard 7.6(9.4/2)                                 06-12-13    AI05-0013-1/03
+!standard 7.6(9.4/2)                                 07-05-17    AI05-0013-1/04
 !standard D.7(4/2)
 !class binding interpretation 06-04-10
 !status ARG Approved  11-0-1  06-11-18
@@ -23,14 +23,14 @@
 the parent object gets finalized, and must therefore have been taken into
 account for computing the "needs finalization" properties.  However:
 
-1 - Coextensions can exist for nonlimited types. Thus, the "limited"
+(1) Coextensions can exist for nonlimited types. Thus, the "limited"
 should be deleted from the wording.
 
-2 - This property cannot be computed at the freezing point of the type
+(2) This property cannot be computed at the freezing point of the type
 (which is the natural place to do so), as the designated type may not
-be frozen yet. Indeed, there is no point during the current compilation
+be frozen yet. Indeed, there is no place during the current compilation
 where it can be computed if the designated type is an incomplete one
-from a limited view - it will not be known until link-time if
+from a limited view - it will not be known until link-time if the
 complete type is controlled.
 
 This definition is used in No_Nested_Finalization; (2) implies link-time
@@ -60,7 +60,7 @@
 
 Directly attempting to fix problem (2) leads into a rat-hole of bad or
 incompatible solutions. (If you are interested, version /01 of this AI
-contained an exhausive list.)
+contained an exhaustive list.)
 
 The key is to fix the uses of "needs finalization" to consider coextensions.
 There is only one use: restriction No_Nested_Finalization. 
@@ -69,7 +69,7 @@
 must be frozen, so there is no problem knowing whether it "needs finalization".
 
 Note that the new rule uses the accessibility level of the access type of the
-allocator. This is needed to take into account coextensions; the accessibility
+allocator. This is needed to take coextensions into account; the accessibility
 level is determined by an extensive set of rules and we certainly don't want to
 duplicate those.
 

Questions? Ask the ACAA Technical Agent