CVS difference for ais/ai-00204.txt

Differences between 1.9 and version 1.10
Log of other versions for file ais/ai-00204.txt

--- ais/ai-00204.txt	2003/05/23 23:24:45	1.9
+++ ais/ai-00204.txt	2004/07/27 23:00:47	1.10
@@ -1,5 +1,7 @@
-!standard B.2      (12)                               03-04-15  AI95-00204/04
+!standard B.2      (12)                               04-07-02  AI95-00204/05
 !class binding interpretation 99-09-24
+!status Amendment 200Y 04-07-02
+!status ARG Approved 10-0-0  04-06-17
 !status work item 99-02-02
 !status received 98-03-27
 !priority High
@@ -30,17 +32,8 @@
 
 !wording
 
-Replace paragraph B.2(12) which states
+Add after B.2(10):
 
-For each implementation-defined convention identifier, there should be a child
-package of package Interfaces with the corresponding name. This package should
-contain any declarations that would be useful for interfacing to the language
-(implementation) represented by the convention. Any declarations useful for
-interfacing to any language on the given hardware architecture should be
-provided directly in Interfaces.
-
-by the following
-
 Support for interfacing to any foreign language is optional. However, an
 implementation shall not provide any attribute, library unit, or pragma
 having the same name as an attribute, library unit, or pragma (respectively)
@@ -49,9 +42,13 @@
 than that required by those clauses. A program that attempts to use an
 unsupported capability of this Annex shall either be identified by the
 implementation before run time or shall raise an exception at run time.
-(This is similar to the requirements regarding the Specialized Needs Annexes,
-see 1.1.3.)
 
+AARM Note
+This is similar to the requirements regarding the Specialized Needs Annexes,
+see 1.1.3.
+
+Add after B.2(11):
+
 A child package of package Interfaces with the name of a convention may
 be provided independently of whether the convention is supported by the
 pragma Convention and vice versa. Such a child package should contain any
@@ -60,6 +57,8 @@
 for interfacing to any language on the given hardware architecture should
 be provided directly in Interfaces.
 
+Delete B2.(12).
+
 !discussion
 
 There are two primary reasons for interfacing to another language such as
@@ -87,16 +86,12 @@
 apply to all the features of this annex such as the package Interfaces itself.
 
 
-!corrigendum B.02(12)
+!corrigendum B.02(10)
 
-@drepl
-For each implementation-defined convention identifier, there should be a child
-package of package Interfaces with the corresponding name. This package should
-contain any declarations that would be useful for interfacing to the language
-(implementation) represented by the convention. Any declarations useful for
-interfacing to any language on the given hardware architecture should be
-provided directly in Interfaces.
-@dby
+@dinsa
+@xbullet<Floating point types corresponding to each floating point format fully
+supported by the hardware.>
+@dinst
 Support for interfacing to any foreign language is optional. However, an
 implementation shall not provide any attribute, library unit, or pragma
 having the same name as an attribute, library unit, or pragma (respectively)
@@ -105,9 +100,14 @@
 than that required by those clauses. A program that attempts to use an
 unsupported capability of this Annex shall either be identified by the
 implementation before run time or shall raise an exception at run time.
-(This is similar to the requirements regarding the Specialized Needs Annexes,
-see 1.1.3.)
 
+!corrigendum B.02(11)
+
+@dinsa
+An implementation may provide implementation-defined library units that are
+children of Interfaces, and may add declarations to the visible part of
+Interfaces in addition to the ones defined above.
+@dinst
 A child package of package Interfaces with the name of a convention may be
 provided independently of whether the convention is supported by the pragma
 Convention and vice versa. Such a child package should contain any declarations
@@ -115,6 +115,16 @@
 represented by the convention. Any declarations useful for interfacing to any
 language on the given hardware architecture should be provided directly in
 Interfaces.
+
+!corrigendum B.02(12)
+
+@ddel
+For each implementation-defined convention identifier, there should be a child
+package of package Interfaces with the corresponding name. This package should
+contain any declarations that would be useful for interfacing to the language
+(implementation) represented by the convention. Any declarations useful for
+interfacing to any language on the given hardware architecture should be
+provided directly in Interfaces.
 
 
 !ACATS test

Questions? Ask the ACAA Technical Agent