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

--- ai05s/ai05-0043-1.txt	2007/07/26 02:58:06	1.3
+++ ai05s/ai05-0043-1.txt	2007/10/09 19:27:15	1.4
@@ -1,4 +1,4 @@
-!standard 11.4.1(10.1/2)                                     07-06-15    AI05-0043-1/01
+!standard 11.4.1(10.1/2)                                     07-10-08    AI05-0043-1/02
 !standard 11(2)
 !class binding interpretation 07-03-27
 !status ARG Approved  8-0-2  07-06-03
@@ -19,7 +19,7 @@
 
 (1) 11(2) says "An exception is raised initially either
 by a raise_statement or by the failure of a language-defined check."
-But this isn't correct any more, since an exception can also be raised
+But this isn't correct (even for Ada 95), since an exception can also be raised
 initially by a Raise_Exception call.
 
 (2) 11.4.1(10.1/2) describes the operation of Ada.Exceptions.Exception_Message.
@@ -30,13 +30,13 @@
 
 !recommendation
 
-(See Summary.)
+(See summary.)
 
 !wording
 
 (1) Modify 11(2):
 
-An exception is raised initially either by a
+An exception is raised initially by a
 raise_statement{, by a call to Raise_Exception,} or by the failure of a
 language-defined check.
 
@@ -60,13 +60,19 @@
 !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.
+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 exception is raised initially either by a
+An @fa<exception_declaration> declares a name for an exception. 
+An exception is raised initially by a
 @fa<raise_statement>, by a call to Raise_Exception, or by the failure of a
-language-defined check.
+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.
 
 !corrigendum 11.4.1(10.1/2)