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

Differences between 1.1 and version 1.2
Log of other versions for file ai12s/ai12-0409-1.txt

--- ai12s/ai12-0409-1.txt	2020/12/04 03:50:26	1.1
+++ ai12s/ai12-0409-1.txt	2020/12/04 07:59:30	1.2
@@ -1,12 +1,19 @@
-!standard 5.5.2(2/3)                                  20-12-03  AI12-0409-1/01
-!standard 5.5.2(5/4)
-!standard 5.5.2(7/3)
+!standard 10.2.1(11.6/2)                                20-12-03  AI12-0409-1/01
+!standard 10.2.1(11.7/3)
+!standard 10.2.1(11.8/2)
+!standard A.18.19(5/5)
+!standard A.18.20(5/5)
+!standard A.18.21(5/5)
+!standard A.18.22(5/5)
+!standard A.18.23(5/5)
+!standard A.18.24(5/5)
+!standard A.18.25(5/5)
 !class Amendment 20-12-03
 !status work item 20-12-03
 !status received 20-11-27
 !priority Low
 !difficulty Easy
-!subject 
+!subject Preelaborable_Initialization and bounded containers
 !summary
 
 We define a Preelaborable_Initialization attribute, which is defined only for 
@@ -57,7 +64,7 @@
     be specified for any type for which the attribute is defined. The
     value shall be specified by a static expression, unless the type is
     not a formal type but is nevertheless declared within a generic
-    package.  In this latter case, the value may also be specified by
+    package. In this latter case, the value may also be specified by
     references to the Preelaborable_Initialization attribute of one or
     more formal types visible at the point of the declaration of the
     composite type, conjoined with "and".
@@ -66,7 +73,7 @@
 
   [The Preelaborable_Initialization aspect shall be directly specified
   only for a composite type declared within the visible part of a
-  package or a generic package.  ]If the Preelaborable_Initialization
+  package or a generic package. ]If the Preelaborable_Initialization
   aspect is specified True for a private type or a private extension,
   the full view of the type shall have preelaborable initialization. If
   the aspect is specified True for a protected type, the protected type
@@ -148,10 +155,10 @@
 
 !discussion
 
-We debated various ways to address this issue.  Although we have abandoned 
+We debated various ways to address this issue. Although we have abandoned 
 the use of attributes for Nonblocking and Global, we felt that for this 
 particular aspect, allowing the use of an attribute was the simplest 
-solution.  We considered defining some additional aspect, or making some
+solution. We considered defining some additional aspect, or making some
 automatic rule, but none of them seemed as simple as this approach, which 
 seemed both intuitive and readable.
 

Questions? Ask the ACAA Technical Agent