CVS difference for ais/ai-00041.txt

Differences between 1.10 and version 1.11
Log of other versions for file ais/ai-00041.txt

--- ais/ai-00041.txt	2000/06/20 04:22:42	1.10
+++ ais/ai-00041.txt	2000/06/21 23:39:06	1.11
@@ -98,20 +98,20 @@
 
 Some general observations:
 
-1. If a pragma that applies to a generic unit were not to apply
-   to all instances, the user would still have the option to
-   specify such a pragma for each of the instances individually.
-   This may be cumbersome, but no language functionality is lost.
-
-2. If a pragma that applies to a generic unit were to apply to
-   all instances automatically, the user would lose the
-   capability of specifying a pragma that applies to the generic
-   unit only.
-   Note that the user does not have the option of placing the
-   pragma outside the generic package and thereby escape a
-   "current instance rule" (discussed later) selectively, since
-   such placement is not allowed for pragmas on generic packages;
-   ARM 10.1.5(4).
+ 1. If a pragma that applies to a generic unit were not to apply
+    to all instances, the user would still have the option to
+    specify such a pragma for each of the instances individually.
+    This may be cumbersome, but no language functionality is lost.
+
+ 2. If a pragma that applies to a generic unit were to apply to
+    all instances automatically, the user would lose the
+    capability of specifying a pragma that applies to the generic
+    unit only.
+    Note that the user does not have the option of placing the
+    pragma outside the generic package and thereby escape a
+    "current instance rule" (discussed later) selectively, since
+    such placement is not allowed for pragmas on generic packages
+    (see 10.1.5(4)).
 
 
 We now examine the pragma semantics for all program unit pragmas
@@ -274,7 +274,7 @@
 Pragma Elaborate_Body applied to generic library unit forces the elaboration
 of the body of the unit immediately after the elaboration of the generic
 declaration.  In the case of instantiations, this effect of the pragma
-merely restates the existing rules on instance elaboration, ARM 12.3(20), so
+merely restates the existing rules on instance elaboration, 12.3(20), so
 that this effect is the rule for instantiations in general. Hence, there is
 no need to make the pragma apply automatically to all instances, while it
 would be most detrimental to enforce as a secondary consequence that such
@@ -293,15 +293,16 @@
 
 Pragma Inline:
 
-Pragma INLINE (historically) subscribes to the rule that it applies to all
+Pragma Inline (historically) subscribes to the rule that it applies to all
 instances, when given for a generic subprogram.  Its application to all
-instances relies on explicitly stated semantics of the pragma; ARM 6.3.2(5).
+instances relies on explicitly stated semantics of the pragma given in 6.3.2(5).
 
 
 Pragmas Convention, Export, Import:
 
 The applicability of these program unit pragmas to generic units is left
-implementation-defined by the ARM. Thus, implementations can choose
+implementation-defined by the International Standard. Thus, implementations
+can choose
 whichever semantics seem most appropriate. Since these pragmas are not
 library unit pragmas, inheritance of the pragma by instances of the generic
 unit does not have the detrimental effects shown earlier in this analysis.
@@ -321,7 +322,7 @@
 contexts.
 
 Finally, we have seen that the existing language-defined program unit pragmas
-that are not library unit pragmas should apply to their instances. For the INLINE
+that are not library unit pragmas should apply to their instances. For the Inline
 pragma, this rule is already explicitly stated. However, as this presently matters
 only in cases, where applicability of the pragma to generic units is
 implementation-defined, and one can equally well conceive of future

Questions? Ask the ACAA Technical Agent