CVS difference for ai05s/ai05-0258-1.txt

Differences between 1.2 and version 1.3
Log of other versions for file ai05s/ai05-0258-1.txt

--- ai05s/ai05-0258-1.txt	2011/06/20 04:55:19	1.2
+++ ai05s/ai05-0258-1.txt	2011/07/29 03:10:20	1.3
@@ -1,6 +1,8 @@
-!standard  11(2/3)                               11-06-19    AI05-0258-1/01
+!standard  11(2/3)                               11-07-28    AI05-0258-1/02
 !standard  11.4.1(10.1/3)
 !class binding interpretation 11-06-19
+!status Amendment 2012 11-07-28
+!status ARG Approved 12-0-0  11-06-25
 !status work item 11-06-16
 !status received 11-04-29
 !priority Low
@@ -9,7 +11,8 @@
 !subject Preserving information in an exception occurrence
 !summary
 
-** TBD.
+The introductory text at the start of section 11 is too specific; the rules
+given in 11.4.1 are the intent.
 
 !question
 
@@ -31,18 +34,41 @@
 
 !wording
 
-** TBD
+Replace the middle sentence of 11(2) with:
 
+An exception can be raised explicitly (for example, by a raise_statement) or
+implicitly (for example, by the failure of a language-defined check).
+
 !discussion
 
+The introductory text is far too specific; if we generalize it, we won't have to
+fix it in the future and we can let 11.4.1(10.1/3) do the exact definition (and
+that leaves some cases unspecified).
+
+!corrigendum 11(2)
+
+@drepl
+An @fa<exception_declaration> declares a name for an exception. 
+An exception is raised initially either by a
+@fa<raise_statement> or by the failure of a
+language-defined check. When an exception arises, control can be transferred to a
+user-provided @fa<exception_handler> at the end of a @fa<handled_sequence_of_statements>,
+or it can be propagated to a dynamically enclosing execution.
+@dby
+An @fa<exception_declaration> declares a name for an exception. 
+An exception can be raised explicitly (for example, by a raise_statement) or
+implicitly (for example, by the failure of a language-defined check).
+When an exception arises, control can be transferred to a
+user-provided @fa<exception_handler> at the end of a @fa<handled_sequence_of_statements>,
+or it can be propagated to a dynamically enclosing execution.
 
 !ACATS Test
 
-** TBD.
+No test needed.
 
 !ASIS
 
-** TBD.
+No ASIS impact.
 
 !appendix
 

Questions? Ask the ACAA Technical Agent