CVS difference for ai12s/ai12-0342-1.txt

Differences between 1.5 and version 1.6
Log of other versions for file ai12s/ai12-0342-1.txt

--- ai12s/ai12-0342-1.txt	2020/01/14 05:15:44	1.5
+++ ai12s/ai12-0342-1.txt	2020/01/16 05:28:53	1.6
@@ -1,9 +1,10 @@
-!standard 4.2.1(0)                                     20-01-11  AI12-0342-1/03
+!standard 4.2.1(0)                                     20-01-15  AI12-0342-1/04
 !standard 6.3.1(22)
 !reference AI12-0249-1
 !reference AI12-0295-1
 !reference AI12-0325-1
 !class Amendment 19-09-10
+!status ARG Approved 9-0-4  20-01-15
 !status work item 19-09-10
 !status received 19-08-15
 !priority Low
@@ -32,7 +33,7 @@
       aspects. These aspects are inherited according to the rules given
       in 13.1. In the case of type extension, any such inherited aspects
       must be overridden.
-   2) Treating a user-defined literal like a function call for purposes
+   2) Treating a user-defined literal like a function call for purposes of
       static semantics, not just dynamic semantics. This is intended to
       clarify, for example, the rules about how user-defined literals interact
       with abstract types and abstract subprograms.
@@ -47,10 +48,10 @@
    "that denotes a primitive function of T" with "that statically denotes a 
     function"
 
-Append after 4.2.1 (5.a/5) (i.e., at the end of the Static Semantics section)
+Append after 4.2.1 (5/5) (at the end of the Static Semantics section)
 
    AARM Ramification:
-      Thus, the following example is legal because the preceding rules
+      The following example is legal because the preceding rules
       are name resolution rules (see 13.1.1):
          package Pkg1 is
             type T is record X, Y : Integer; end record
@@ -104,11 +105,12 @@
 
    Such a literal is said to be a "user-defined literal".
 
-Append after 4.2.1(6/5) (i.e., at the end of the Legality Rules section)
+Append after 4.2.1(6/5) (at the end of the Legality Rules section)
 
-   If a nonabstract tagged type inherits any of these three aspects,
-   then each inherited aspect shall be overridden.
- 
+   If a nonabstract tagged type other than a null extension inherits any of
+   these three aspects, then each inherited aspect shall be directly 
+   specified for the type.
+
 Delete 4.2.1(7-8/5).
    [This is the entire Dynamic Semantics section (it is now redundant).]
 
@@ -128,7 +130,7 @@
 
 !discussion
 
-Because these are aspects, we don't get reemergence for with
+Because these are aspects, we don't get reemergence with
 formal derived types (the way that we might with primitive
 subprograms). That means that in this example,
    procedure Proc is

Questions? Ask the ACAA Technical Agent