CVS difference for ais/ai-00230.txt

--- ais/ai-00230.txt	2004/01/23 04:59:23	1.14
+++ ais/ai-00230.txt	2004/02/06 05:01:47	1.15
@@ -1,4 +1,4 @@
-!standard 03.04.01(06)                               04-01-09  AI95-00230/10
+!standard 03.04.01(06)                               04-02-05  AI95-00230/11
 !standard 03.06(07)
 !standard 03.06(22/1)
 !standard 03.07(10)
@@ -434,10 +434,6 @@
 Similarly, issues relating to supporting access-to-constant and
 null-allowing anonymous access types are in AI-00231.
 
-We also fix an RM bug here; 3.4.1(3) says that all types are either specific,
-class-wide, or universal, but then fails to include access_definition (for
-anonymous access types) in any of those categories.
-
 Implementation Issues:
 
 Object renaming declarations with access_definitions are no harder to
@@ -2287,6 +2283,29 @@
 to that AI. AI-231 should be written to presume that AI-230 is approved (as it
 is ahead of AI-231 in the ARG process); in particular, the needed change to
 8.5.1(4) should be included in AI-231.
+
+*************************************************************
+
+From: Javier Miranda
+Sent: Tuesday, January 27, 2004  10:50 AM
+
+Following paragraph was removed from version 1.13 to version 1.14:
+
+-Change 3.4.1(3) as follows:
+-
+-   Every type is either a specific type, a class-wide type, or a universal
+-   type. A specific type is one defined by a type_declaration, a
+-   formal_type_declaration, an access_definition, or a full type definition
+-   embedded in a declaration for an object. Class-wide and universal types are
+-   implicitly defined, to act as representatives for an entire class of types,
+-   as follows:
+
+As a consequence, following paragraph (in the !discussion section)
+should also be removed:
+
+"We also fix an RM bug here; 3.4.1(3) says that all types are either specific,
+ class-wide, or universal, but then fails to include access_definition (for
+ anonymous access types) in any of those categories."
 
 *************************************************************