CVS difference for ais/ai-50217.txt

Differences between 1.22 and version 1.23
Log of other versions for file ais/ai-50217.txt

--- ais/ai-50217.txt	2005/08/04 00:54:14	1.22
+++ ais/ai-50217.txt	2005/08/21 06:00:50	1.23
@@ -1,13 +1,15 @@
-!standard 10.01.01   (12)                           05-06-20  AI95-00217-06/15
+!standard 10.01.01   (12)                           05-08-03  AI95-00217-06/16
 !standard 10.01.01   (15)
 !standard 10.01.01   (26)
 !standard 10.01.02   (04)
 !standard 10.01.02   (06)
 !standard 10.01.02   (08)
+!standard 10.01.02   (09)
 !standard 10.01.04   (03)
 !standard 10.01.04   (06)
 !standard 10.01.06   (02)
 !standard 10.02      (06)
+!standard 10.02.01   (25)
 !standard  3.10.01   (10)
 !standard  4.01      (09)
 !standard  8.03      (20)
@@ -232,6 +234,21 @@
 way such a dependence can be broken.
 End AARM Note.
 
+Replace 10.1.2(9) with:
+
+A library_item mentioned in a nonlimited_with_clause of a compilation unit is
+visible within the compilation unit and hence acts just like an ordinary
+declaration. Thus, within a compilation unit that mentions its declaration,
+the name of a library package can be given in use_clauses and can be used to
+form expanded names, a library subprogram can be called, and instances of a
+generic library unit can be declared. If a child of a parent generic package
+is mentioned in a nonlimited_with_clause, then the corresponding declaration
+nested within each visible instance is visible within the compilation unit.
+Similarly, a library_item mentioned in a limited_with_clause of a
+compilation unit is visible within the compilation unit and thus can be used to
+form expanded names.
+
+
 Add after 10.1.4(3):
 
 The mechanisms for adding a unit mentioned in a limited_with_clause to an
@@ -262,6 +279,11 @@
    package is needed, then so is the explicit declaration of the
    library package.
 
+Add after 10.2.1(25):
+
+The library_unit_name of a pragma Elaborate or Elaborate_All
+shall denote a nonlimited view of a library unit.
+
 !discussion
 
 It is natural to think of a with_clause as causing a library unit to become
@@ -774,6 +796,30 @@
 @fa<use_clause> that names an entity declared within the declarative region of
 the library package.>
 
+!corrigendum 10.1.2(9)
+
+@drepl
+A @fa<library_item> mentioned in a @fa<with_clause> of a compilation unit
+is visible within the compilation unit and hence acts just like an ordinary
+declaration. Thus, within a compilation unit that mentions its declaration,
+the name of a library package can be given in @fa<use_clause>s and can be used
+to form expanded names, a library subprogram can be called, and instances of a
+generic library unit can be declared. If a child of a parent generic package
+is mentioned in a @fa<with_clause>, then the corresponding declaration nested
+within each visible instance is visible within the compilation unit.
+@dby
+A @fa<library_item> mentioned in a @fa<nonlimited_with_clause> of a compilation
+unit is visible within the compilation unit and hence acts just like an
+ordinary declaration. Thus, within a compilation unit that mentions its
+declaration, the name of a library package can be given in @fa<use_clause>s and
+can be used to form expanded names, a library subprogram can be called, and
+instances of a generic library unit can be declared. If a child of a parent
+generic package is mentioned in a @fa<nonlimited_with_clause>, then the
+corresponding declaration nested within each visible instance is visible
+within the compilation unit. Similarly, a @fa<library_item> mentioned in a
+@fa<limited_with_clause> of a compilation unit is visible within the
+compilation unit and thus can be used to form expanded names.
+
 !corrigendum 10.1.4(3)
 
 @drepl
@@ -832,6 +878,15 @@
 package is needed, then so is the explicit declaration of the
 library package.>
 
+!corrigendum 10.2.1(25)
+
+@dinsa
+If a @fa<pragma> Elaborate_Body applies to a declaration, then the declaration
+requires a completion (a body).
+@dinst
+The @i<library_unit_>@fa<name> of a @fa<pragma> Elaborate or Elaborate_All
+shall denote a nonlimited view of a library unit.
+
 !appendix
 
 From: Pascal Leroy
@@ -3975,7 +4030,7 @@
 -----------------
 Thoughts on the implementation of "limited with" in AdaMagic
 
-          $Revision: 1.22 $ $Date: 2005/08/04 00:54:14 $
+          $Revision: 1.23 $ $Date: 2005/08/21 06:00:50 $
 
 The "limited with" clause makes a "limited view"
 of a package visible in the compilation unit
@@ -5784,7 +5839,7 @@
 -----------------
 Thoughts on the implementation of "limited with" in AdaMagic
 
-          $Revision: 1.22 $ $Date: 2005/08/04 00:54:14 $
+          $Revision: 1.23 $ $Date: 2005/08/21 06:00:50 $
 
 The "limited with" clause makes a "limited view"
 of a package visible in the compilation unit

Questions? Ask the ACAA Technical Agent