CVS difference for ais/ai-00161.txt

Differences between 1.18 and version 1.19
Log of other versions for file ais/ai-00161.txt

--- ais/ai-00161.txt	2005/08/05 04:31:29	1.18
+++ ais/ai-00161.txt	2005/10/31 05:18:08	1.19
@@ -1,4 +1,4 @@
-!standard 10.02.01 (04)                               05-07-07  AI95-00161/11
+!standard 10.02.01 (04)                               05-10-10  AI95-00161/12
 !standard 10.02.01 (09)
 !standard 10.02.01 (11)
 !standard  7.06 (05)
@@ -61,7 +61,7 @@
 !wording
 
 Change the 10.2.1(9) to read:  "The creation of an object (including a
-component) of a type which does not have preelaborable initialization.
+component) of a type that does not have preelaborable initialization.
 Similarly, the evaluation of an extension_aggregate with an ancestor
 subtype_mark denoting a subtype of such a type."
 
@@ -102,15 +102,16 @@
 
 This pragma must appear in the visible part of a package or generic package.
 
-If the pragma appears in the first list of declarative_items of a
+If the pragma appears in the first list of basic_declarative_items of a
 package_specification, then the direct_name shall denote the first subtype of a
 private type, private extension, or protected type without entry_declarations,
-and the type shall be declared within the same package as the pragma. If the
-pragma is applied to a private type or a private extension, the full view of
-the type shall have preelaborable initialization. If the pragma is applied to a
-protected type, each component of the protected type shall have preelaborable
-initialization. In addition to the places where Legality Rules normally apply,
-these rules apply also in the private part of an instance of a generic unit.
+and the type shall be declared immediately within the same package as the
+pragma. If the pragma is applied to a private type or a private extension, the
+full view of the type shall have preelaborable initialization. If the pragma is
+applied to a protected type, each component of the protected type shall have
+preelaborable initialization. In addition to the places where Legality Rules
+normally apply, these rules apply also in the private part of an instance of a
+generic unit.
 
 If the pragma appears in a generic_formal_part, then the direct_name shall
 denote a generic formal private type or a generic formal derived type declared
@@ -206,9 +207,10 @@
 @dinsa
 @xindent<A @fa<pragma> Preelaborate is a library unit pragma.>
 @dinss
-@xindent<The form of a @fa<pragma> Preelaborable_Initialization is as follows:@hr
-     @b<pragma> Preelaborable_Initialization (@fa<direct_name>);>
+@xindent<The form of a @fa<pragma> Preelaborable_Initialization is as follows:>
 
+@xindent<@ @b<pragma> Preelaborable_Initialization(@fa<direct_name>);>
+
 !corrigendum 10.02.01(9)
 
 @drepl
@@ -218,7 +220,7 @@
 @fa<extension_aggregate> with an ancestor @fa<subtype_mark> denoting a subtype
 of such a type.>
 @dby
-@xbullet<The creation of an object (including a component) of a type which does
+@xbullet<The creation of an object (including a component) of a type that does
 not have preelaborable initialization. Similarly, the evaluation of an
 @fa<extension_aggregate> with an ancestor @fa<subtype_mark> denoting a subtype
 of such a type.>
@@ -267,12 +269,12 @@
 preelaborable initialization. This pragma shall appear in the visible part
 of a package or generic package.
 
-If the pragma appears in the first list of declarative_items of a
+If the pragma appears in the first list of @fa<basic_declarative_item>s of a
 @fa<package_specification>, then the @fa<direct_name> shall denote the first
 subtype of a private type, private extension, or protected type without
-@fa<entry_declaration>s, and the type shall be declared within the same package
-as the @fa<pragma>. If the @fa<pragma> is applied to a private type or a
-private extension, the full view of the type shall have preelaborable
+@fa<entry_declaration>s, and the type shall be declared immediately within the
+same package as the @fa<pragma>. If the @fa<pragma> is applied to a private
+type or a private extension, the full view of the type shall have preelaborable
 initialization. If the @fa<pragma> is applied to a protected type, each
 component of the protected type shall have preelaborable initialization. In
 addition to the places where Legality Rules normally apply, these rules apply
@@ -363,10 +365,10 @@
 !corrigendum  B.3.1(05)
 
 @drepl
-@xcode<    @b<type> Chars_Ptr @b<is private>;>
+@xcode<    @b<type> chars_ptr @b<is private>;>
 @dby
-@xcode<    @b<type> Chars_Ptr @b<is private>;
-    @b<pragma> Preelaborable_Initialization(Chars_Ptr);>
+@xcode<    @b<type> chars_ptr @b<is private>;
+    @b<pragma> Preelaborable_Initialization(chars_ptr);>
 
 !corrigendum C.4(4)
 

Questions? Ask the ACAA Technical Agent