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

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

--- ai05s/ai05-0013-1.txt	2008/05/10 05:14:33	1.13
+++ ai05s/ai05-0013-1.txt	2008/05/29 04:36:46	1.14
@@ -1,4 +1,4 @@
-!standard 7.6(9.4/2)                                 08-04-09    AI05-0013-1/12
+!standard 7.6(9.4/2)                                 08-05-21    AI05-0013-1/13
 !standard 13.12(8)
 !standard D.7(3)
 !standard D.7(4/2)
@@ -23,6 +23,8 @@
 access types which designate types that need finalization, and delete the
 coextension rule from the definition of "needs finalization".
 
+Class-wide types are defined to "need finalization".
+
 Correct the restrictions wording to avoid "shall" as these are definitions.
 
 Clarify when (if ever) restrictions are checked.
@@ -83,7 +85,7 @@
           behavior associated with a violation of the requirement.
 
           AARM Ramification: In this latter case, there is no post-compilation
-              check required.
+              check needed for the requirement.
    
 Replace D.7(3) with:
    No task depends on a task other than the environment task of
@@ -143,6 +145,12 @@
 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.
+
+While reviewing the "needs finalization" wording, it was pointed out that
+it is impossible to tell statically if a class-wide type includes a controlled
+part (because some future extension may include such a part, including one not
+yet written). As such, all class-wide types have to be treated as if they
+need finalization, and a sentence was added to that effect.
 
 During editorial review it was noted that the wording of D.7 is weird
 because it uses sometimes "shall" and sometimes "is".  This is 

Questions? Ask the ACAA Technical Agent