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

--- ai05s/ai05-0053-1.txt	2008/05/10 05:14:33	1.5
+++ ai05s/ai05-0053-1.txt	2008/05/22 05:23:58	1.6
@@ -1,6 +1,7 @@
-!standard 3.10(9/2)                                08-04-09    AI05-0053-1/05
+!standard 3.10(9/2)                                08-05-21    AI05-0053-1/06
 !standard 6.5(2.1/2)
 !class binding interpretation 07-05-15
+!status work item 08-05-21
 !status ARG Approved  8-0-0  08-02-09
 !status work item 07-05-15
 !status received 07-05-07
@@ -37,8 +38,8 @@
    a task type, or a type that has the reserved word *limited* in its
    full definition is also defined to be aliased.
 with
-   The current instance of an immutably limited type is defined to be
-   aliased, as is the return object of an extended_return_statement
+   The current instance of an immutably limited type (see 7.5) is defined
+   to be aliased, as is the return object of an extended_return_statement
    (see 6.5) that is of an immutably limited type.
 
 In 6.5(2.1/2) (syntax for extended_return_statement), delete "[aliased]".
@@ -206,8 +207,8 @@
 @b<aliased>, or by a renaming of an aliased view. In addition, the dereference
 of an access-to-object value denotes an aliased view, as does a view conversion
 (see 4.6) of an aliased view. The current instance of an immutably limited type
-is defined to be aliased, as is the return object of an @fa<extended_return_statement>
-(see 6.5) that is of an immutably limited type.
+(see 7.5) is defined to be aliased, as is the return object of
+an @fa<extended_return_statement> (see 6.5) that is of an immutably limited type.
 Finally, a formal parameter or generic formal object of a tagged type is
 defined to be aliased. Aliased views are the ones that can be designated by
 an access value.
@@ -280,4 +281,14 @@
 there are lots of other unintended consequences (like the incomparability of accessibility
 in some cases) that are a lot harder to implement and have a lot more impact.
 
-****************************************************************
\ No newline at end of file
+****************************************************************
+
+Editor's note, May 21, 2008
+
+This AI was withdrawn from WG 9 consideration as AI05-0052-1, on which it depends,
+was found to be seriously flawed. I do not believe that there is any actual problem
+with this AI, only that it depends on a broken definition. (Indeed, this AI *would*
+be broken with the original definition of AI-52, according to Pascal Leroy -- see
+the discussion in the !appendix of AI-52.)
+
+****************************************************************