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

Differences between 1.3 and version 1.4
Log of other versions for file ai12s/ai12-0003-1.txt

--- ai12s/ai12-0003-1.txt	2013/02/01 05:50:19	1.3
+++ ai12s/ai12-0003-1.txt	2013/05/09 02:08:40	1.4
@@ -1,4 +1,4 @@
-!standard 3.10.2(13.2/3)                             12-12-01    AI12-0003-1/02
+!standard 3.10.2(13.2/3)                             13-05-08    AI12-0003-1/03
 !standard 13.11.3(1/3)
 !standard 13.11.3(3.1/3)
 !standard 13.11.3(4.1/3)
@@ -29,6 +29,15 @@
+Append after 8.2(11) (i.e., as a new paragraph at the end of 
+the static semantics section):
+   The immediate scope of a pragma which is not used
+   as a configuration pragma is defined to be the
+   region extending from immediately after the pragma
+   to end of the pragma's nearest enclosing declarative
+   region.
 Reinstate 13.11.3 (1/4) to read:
 Two storage pool pragmas can be used to control the setting of a
 default storage pool for access types: Default_Storage_Pool and
@@ -85,15 +94,6 @@
  within the immediate scope of another {storage pool} pragma[
-<<<<< Aside: This and the other paragraphs of the section have a problem:
-"immediate scope" of pragmas is not defined ("immediate scope" is defined only
-for declarations and for (declared) entitites. See 8.2. >>>>
-<<<<<< Aside 2: This issue of contradictory pragmas surely is not
-limited to the storage pool pragmas. 2a) has anybody checked the
-manual for problems with other pragmas. 2b) shouldn't this be a
-general rule on configuration pragmas?  >>>>>
 Modify 13.11.3 (5/3) to read
  This aspect overrides any {storage pool}[Default_Storage_Pool] pragma
  that might apply to the generic unit.
@@ -113,9 +113,6 @@
 A pragma that causes the implementation to revert to the standard
 allocation method seemed best to achieve the desired capability.
-<<<< Note the slightly unrelated problems discovered in 13.11.3 and
-particularly (4.2/3), as described in the proposal text. >>>>
 !ACATS test

Questions? Ask the ACAA Technical Agent