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

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

--- ai12s/ai12-0309-1.txt	2019/02/07 02:06:39	1.2
+++ ai12s/ai12-0309-1.txt	2019/02/13 05:25:32	1.3
@@ -1,9 +1,11 @@
-!standard 11.5(10)                                      19-02-05  AI12-0309-1/01
+!standard 11.5(10)                                      19-02-12  AI12-0309-1/02
 !standard 11.5(19)
 !standard 11.5(20)
 !standard 11.5(22)
 !standard 11.5(24)
 !class binding interpretation 19-02-05
+!status Amendment 1-2012 19-02-12
+!status ARG Approved 7-1-2  19-02-12
 !status work item 19-02-05
 !status received 18-11-28
 !priority Low
@@ -39,12 +41,12 @@
 Add after 11.5(20):
 
 Program_Error_Check
-   Check that there is not an error in the logic of the program: that subtypes
+   Other language-defined checks that raise Program_Error: that subtypes
    with predicates are not used to index an array in a generic unit;
    that the maximum number of chunks is greater than zero; that the
-   default value of an out parameter is convertable; that there is misuse 
+   default value of an out parameter is convertible; that there is no misuse 
    of functions in a generic with an class-wide actual type; that there are
-   not colliding External_Tag values; that there is misuse of operations of 
+   not colliding External_Tag values; that there is no misuse of operations of 
    unchecked union types.
 
 [Note to editor: One needs to add @IndexCheck{Program_Error_Check} to each
@@ -70,12 +72,12 @@
 The following check corresponds to all situations in which any 
 predefined exception is raised {upon failure of a check}.
 
-Modify 11.5(25.a):
+Modify AARM 11.5(25.a):
 
-  All_Checks includes both language-defined and implementation-defined 
-  checks {those with names}.{ It does not include, however, explicit
-  raises of predefined exceptions, nor those propagated from 
-  language-defined subprograms.}
+  All_Checks {may include}[includes both language-defined and]
+  implementation-defined checks.{ It does not include, however, explicit
+  raises of predefined exceptions (including those mandated for language
+  constructs), nor those propagated from language-defined subprograms.}
 
   [Editor's note: The RM consistently (with a handful of exceptions) uses
   the wording "Blah_Error is propagated" rather than "a check is made,
@@ -142,14 +144,13 @@
 written very often.
 
 An alternative would be to make all of the names end in "_Checks", and put the
-existing names that end in "_Check" into Annex J. This would work, but seems
-would be able to remember that
+existing names that end in "_Check" into Annex J. This would work, but this 
+would be a lot of unrequired change.
 
-
 ---
 
 Additionally, the wording in 11.5 associated with the check names can make a 
-causal reader think that these apply to cases that are not intended (explicit 
+casual reader think that these apply to cases that are not intended (explicit 
 raises, exceptions raised by language-defined units, and so on). We correct
 the wording to avoid that. (We worry about this as this list of checks is
 often referred to directly from the index without looking at the complete
@@ -168,6 +169,74 @@
 that Suppress(Bounded_Checks) means that any bounded error that occurred
 should be erroneous. Since it isn't important to answer this question now,
 we pass.
+
+!corrigendum 11.5(10)
+
+@drepl
+@xbullet<The following checks correspond to situations in which the exception 
+Constraint_Error is raised upon failure.>
+@dby
+@xbullet<The following checks correspond to situations in which the exception 
+Constraint_Error is raised upon failure of a language-defined check.>
+
+!corrigendum 11.5(19)
+
+@drepl
+@xbullet<The following checks correspond to situations in which the exception 
+Program_Error is raised upon failure.>
+@dby
+@xbullet<The following checks correspond to situations in which the exception 
+Program_Error is raised upon failure of a language-defined check.>
+
+!corrigendum 11.5(20)
+
+@dinsa
+@xhang<@xterm<Elaboration_Check>When a subprogram or protected entry is called, 
+a task activation is accomplished, or a generic instantiation is elaborated, 
+check that the body of the corresponding unit has already been elaborated.>
+@dinst
+@xhang<@xterm<Program_Error_Check>
+Other language-defined checks that raise Program_Error: that subtypes
+with predicates are not used to index an array in a generic unit;
+that the maximum number of chunks is greater than zero; that the
+default value of an out parameter is convertible; that there is no misuse 
+of functions in a generic with an class-wide actual type; that there are
+not colliding External_Tag values; that there is no misuse of operations of 
+unchecked union types.>
+
+!corrigendum 11.5(22)
+
+@drepl
+@xbullet<The following check corresponds to situations in which the exception 
+Storage_Error is raised upon failure.>
+@dby
+@xbullet<The following check corresponds to situations in which the exception 
+Storage_Error is raised upon failure of a language-defined check.>
+
+!corrigendum 11.5(23)
+
+@dinsa
+@xhang<@xterm<Storage_Check>
+Check that evaluation of an @fa<allocator> does not require more space than 
+is available for a storage pool. Check that the space available for a task 
+or subprogram has not been exceeded.>
+@dinss
+@xbullet<The following check corresponds to situations in which the exception 
+Tasking_Error is raised upon failure of a language-defined check.>
+
+@xhang<@xterm<Tasking_Check>
+Check that all tasks activated successfully. Check that a called task
+has not yet terminated.>
+
+!corrigendum 11.5(24)
+
+@drepl
+@xbullet<The following check corresponds to all situations in which any 
+predefined exception is raised.>
+@dby
+@xbullet<The following check corresponds to all situations in which any 
+predefined exception is raised upon failure of a check.>
+
 
 !ASIS
 

Questions? Ask the ACAA Technical Agent