CVS difference for ai22s/ai22-0029-1.txt

Differences between 1.1 and version 1.2
Log of other versions for file ai22s/ai22-0029-1.txt

--- ai22s/ai22-0029-1.txt	2022/01/25 06:28:32	1.1
+++ ai22s/ai22-0029-1.txt	2022/01/26 00:33:19	1.2
@@ -1,4 +1,4 @@
-!standard 13.3(75.1/3)                                   22-01-24  AI22-0029-1/01
+!standard 13.3(75.1/3)                                   22-01-25  AI22-0029-1/02
 !standard 13.3(76)
 !class binding interpretation 22-01-24
 !status work item 22-01-24
@@ -58,7 +58,7 @@
    This check is on a *pair* of types, and the exception can be raised at
    any of the prescribed points. However, the check cannot be performed
    before both types exist, so that constrains when the exception can be
-   raised. Iin the case where one of the types is declared in a subprogram
+   raised. In the case where one of the types is declared in a subprogram
    while the other is declared at library level, the exception cannot be
    raised until the subprogram is called and its declarations elaborated.
 
@@ -66,7 +66,7 @@
 
    In an implementation, the default external tag for each specific tagged
    type declared in a partition shall be distinct, so long as the type is 
-   declared {by a unique declaration and is }outside an instance of a 
+   declared {by a distinct declaration and is }outside an instance of a 
    generic body. If the compilation unit in which a given tagged type is 
    declared, and all compilation units on which it semantically depends, are
    the same in two different partitions, then the external tag for the type
@@ -79,10 +79,10 @@
 Add after AARM 13.3(76.e): [still as part of the Ramification]
 
    If a single type declaration is elaborated multiple times, the default 
-   external tags need not be different. Note that if such identical tags are
-   used, they cannot raise Program_Error; the check that requires different
-   External_Tags specifically excludes types that come from the same
-   declaration.
+   external tags need not be different. Note that if such identical tags are 
+   used for two different elaborations of the same declaration, they cannot 
+   raise Program_Error; the check that requires different External_Tags
+   specifically excludes types that come from the same declaration.
 
 !discussion
 
@@ -91,7 +91,7 @@
 doesn't matter which type is elaborated first.
 
 Types are created when they are elaborated (3.2.1(11)), and cease to exist
-when their master is is left (7.6.1(11/3)). This check can only be made when
+when their master is left (7.6.1(11/3)). This check can only be made when
 both types exist. Thus, for types not declared at library-level, the check
 will have to be made during their elaboration. This is important, as a type
 that never exists should not cause a program failure.

Questions? Ask the ACAA Technical Agent