CVS difference for ais/ai-00190.txt

Differences between 1.5 and version 1.6
Log of other versions for file ais/ai-00190.txt

--- ais/ai-00190.txt	1999/06/22 01:44:37	1.5
+++ ais/ai-00190.txt	1999/07/28 00:08:45	1.6
@@ -1,6 +1,7 @@
-!standard 13.12(0) (00)                               99-06-12  AI95-00190/02
+!standard 13.12(0) (00)                               99-07-27  AI95-00190/03
 !standard D.7 (15)
 !class binding interpretation 98-10-09
+!status Corrigendum 2000 99-07-27
 !status WG9 approved 99-06-12
 !status ARG approved (6-0-0) 98-10-09
 !status work item 98-09-26
@@ -9,7 +10,7 @@
 !difficulty Hard
 !subject Compile-time enforcement of pragma Restrictions
 
-!summary 99-02-05
+!summary
 
 Whenever enforcement of a restriction imposed by pragma Restrictions
 is not required by the Standard prior to execution, but left to
@@ -18,19 +19,19 @@
 implementation-defined behaviour, provided that every execution of the
 partition will violate the restriction.
 
-!question 99-02-05
+!question
 
 Shall we allow implementations to reject (i.e. refuse to run) programs
 that have run-time detected violations of pragma Restrictions, when they
 are detectable at compile time? (Yes.)
 
-!recommendation 99-02-05
+!recommendation
 
 (see summary)
 
-!wording 99-02-05
+!wording
 
-add an Implementation Permission after 13.12(9):
+Add an Implementation Permission after 13.12(9):
 
 "Whenever enforcement of a restriction is not required prior to
 execution, but left to implementation-defined behaviour of dynamic
@@ -38,7 +39,7 @@
 execution of a partition to which the restriction applies, provided
 that every execution of the partition would violate the restriction."
 
-!discussion 98-09-26
+!discussion
 
 For the particularly critical rejection of programs that violate
 restrictions imposed by pragma Restrictions, the Standard provides for
@@ -51,8 +52,25 @@
 exception but does not specify the place where such an exception is to
 be raised.
 
+!corrigendum 13.12(9)
 
-!appendix 97-08-19
+@dinsa
+An implementation may place limitations on the values of the expression
+that are supported, and limitations on the supported combinations of
+restrictions. The consequences of violating such limitations are
+implementation defined.
+@dinst
+Whenever enforcement of a restriction is not required prior to
+execution, but left to implementation-defined behavior of dynamic
+semantics, an implementation may enforce the restriction prior to
+execution of a partition to which the restriction applies, provided
+that every execution of the partition would violate the restriction.
+
+!ACATS test
+
+This is not testable, as is an implementation permission.
+
+!appendix
 
 !section 13.12(0)
 !subject rejecting violations of pragma Restrictions

Questions? Ask the ACAA Technical Agent