CVS difference for ai12s/ai12-0054-2.txt
--- ai12s/ai12-0054-2.txt 2013/07/18 05:05:31 1.6
+++ ai12s/ai12-0054-2.txt 2013/10/08 00:37:45 1.7
@@ -1,4 +1,4 @@
-!standard 3.2.4(14/3) 13-07-05 AI12-0054-2/04
+!standard 3.2.4(14/3) 13-10-07 AI12-0054-2/05
!class binding interpretation 13-05-31
@@ -147,11 +147,11 @@
to be associated with the Assertion_Error.
The expression of the Predicate_Failure aspect can be as simple as a
-string litteral if all that is desired is to change the message; note
+string literal if all that is desired is to change the message; note
that the current instance of the subtype is visible in the
Predicate_Failure expression -- this can be useful in the exception
message. On the other hand, the expression could be a complicated
-function call to log the bad value for example.
+function call to log the bad value, for example.
If the evaluation of the expression raises an exception (an especially
if it is a raise expression), the exception will propagate normally,
@@ -198,7 +198,7 @@
If we didn't include the Predicate_Failure aspect with a raise_expression here,
using the predicate would change the exception raised on this failure. That
could cause the exception to fall into a different handler than currently, which
-is likely to not be acceptable.
+is unlikely to be acceptable.
We could have used a precondition on Show_Window instead of defining a
predicate. In that case, we'd use the raise_expression directly in the
Questions? Ask the ACAA Technical Agent