CVS difference for ais/ai-00136.txt

Differences between 1.1 and version 1.2
Log of other versions for file ais/ai-00136.txt

--- ais/ai-00136.txt	1998/09/30 00:17:24	1.1
+++ ais/ai-00136.txt	1999/06/26 01:11:13	1.2
@@ -1,5 +1,6 @@
-!standard 10.01.05 (05)                               96-11-16  AI95-00136/05
+!standard 10.01.05 (05)                               99-06-25  AI95-00136/06
 !class binding interpretation 96-05-07
+!status Corrigendum 2000 99-05-27
 !status WG9 approved 96-12-07
 !status ARG approved 12-0-0  96-10-07
 !status ARG approved (subj. ed. rev., letter ballot was 12-0-0) 96-10-03
@@ -10,13 +11,13 @@
 !difficulty Easy
 !subject Placement of Program Unit Pragmas in Generic Packages
 
-!summary 96-09-15
+!summary
 
 A program unit pragma for a generic package must appear at the beginning
 of the package specification, and not in the generic formal part.  For
 any program unit, such a pragma must not appear in the private part.
 
-!question 96-09-15
+!question
 
 Consider:
 
@@ -46,11 +47,11 @@
        pragma Pure; -- Legal? (No.)
    end P;
 
-!recommendation 96-05-08
+!recommendation
 
 (See summary.)
 
-!wording 96-09-15
+!wording
 
 Modify 10.1.5(5):
 
@@ -60,7 +61,7 @@
        direct_name that denotes the immediately enclosing program unit
        declaration.
 
-!discussion 96-09-15
+!discussion
 
 It was not the intent to allow or require a program unit pragma for a
 generic package at the beginning of the generic formal part.
@@ -76,7 +77,30 @@
 Note that for a generic unit, the term "visible part" officially
 includes the generic formal part.
 
-!appendix 96-05-07
+!corrigendum 10.01.05(5)
+
+@drepl
+@xbullet<
+Immediately within the declaration of a program unit and before
+any nested declaration, in which case the argument, if any, shall
+be a @fa<direct_name> that denotes the immediately enclosing program
+unit declaration.>
+@dby
+@xbullet<
+Immediately within the visible part of a program
+unit and before any nested declaration (but not within a generic
+formal part), in which case the argument, if any, shall be a
+@fa<direct_name> that denotes the immediately enclosing program unit
+declaration.>
+
+!ACATS test
+
+A B-Test should be created to insure that program unit pragmas are not given in
+the formal part of a generic package or private part of a package. A C-Test
+should be created to check that program unit pragmas can be given in a
+generic package.
+
+!appendix
 
 !section 10.1.5(05)
 !subject Placement of Program Unit Pragma

Questions? Ask the ACAA Technical Agent