CVS difference for ais/ai-00230.txt

Differences between 1.27 and version 1.28
Log of other versions for file ais/ai-00230.txt

--- ais/ai-00230.txt	2005/10/31 05:18:12	1.27
+++ ais/ai-00230.txt	2005/12/15 02:43:49	1.28
@@ -1,4 +1,4 @@
-!standard 03.04.01(06)                               05-09-30  AI95-00230/19
+!standard 03.04.01(06)                               05-11-30  AI95-00230/20
 !standard 03.02.01(07)
 !standard 03.02.01(08)
 !standard 03.04.01(03)
@@ -308,14 +308,14 @@
               Legality Rules
 
    At least one of the operands of the equality operators for
-   universal_access shall be null, or both shall be
-   access-to-object types, or both shall be access-to-subprogram
+   universal_access shall be of type universal_access, or both shall be
+   of access-to-object types, or both shall be of access-to-subprogram
    types. Further:
-   *  When both are access-to-object types, the
+   *  When both are of access-to-object types, the
       designated types shall be the same or one shall cover the
       other, and if the designated types are elementary or array types,
       then the designated subtypes shall statically match;
-   *  When both are access-to-subprogram types,
+   *  When both are of access-to-subprogram types,
       the designated profiles shall be subtype conformant.
 
 
@@ -659,7 +659,7 @@
 with class-wide types, if a formal parameter is of a universal type, then an
 actual parameter of any type in the corresponding class is acceptable. In
 addition, a value of a universal type (including an integer or real
-@fa<numeric_literal>) is ``universal'' in that it is acceptable where some
+@fa<numeric_literal>) is "universal" in that it is acceptable where some
 particular type in the class is expected (see 8.6).>
 @dby
 @xhang<@xterm<Universal types>
@@ -671,7 +671,7 @@
 parameter is of a universal type, then an actual parameter of any type in the
 corresponding
 class is acceptable. In addition, a value of a universal type (including an
-integer or real @fa<numeric_literal>, or the literal @b<null>) is ``universal''
+integer or real @fa<numeric_literal>, or the literal @b<null>) is "universal"
 in that it is acceptable where some particular type in the class is
 expected (see 8.6).>
 
@@ -927,14 +927,14 @@
 @i<@s8<Legality Rules>>
 
 At least one of the operands of the equality operators for
-@i<universal_access> shall be null, or both shall be
-access-to-object types, or both shall be access-to-subprogram
+@i<universal_access> shall be of type @i<universal_access>, or both shall be
+of access-to-object types, or both shall be of access-to-subprogram
 types. Further:
-@xbullet<When both are access-to-object types, the
+@xbullet<When both are of access-to-object types, the
 designated types shall be the same or one shall cover the
 other, and if the designated types are elementary or array types,
 then the designated subtypes shall statically match;>
-@xbullet<When both are access-to-subprogram types,
+@xbullet<When both are of access-to-subprogram types,
 the designated profiles shall be subtype conformant.>
 
 !corrigendum 4.6(13)

Questions? Ask the ACAA Technical Agent