From d376db7a1e5c411f704400c882edabf84e9befa2 Mon Sep 17 00:00:00 2001 From: ysn Date: Wed, 9 Dec 2015 14:55:16 +0300 Subject: [PATCH] 0026926: Small mistake in the exceptions part of Foundation Classes User's Guide A minor clarification --- dox/user_guides/foundation_classes/foundation_classes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dox/user_guides/foundation_classes/foundation_classes.md b/dox/user_guides/foundation_classes/foundation_classes.md index d39d9b05dc..ce350dbd8f 100644 --- a/dox/user_guides/foundation_classes/foundation_classes.md +++ b/dox/user_guides/foundation_classes/foundation_classes.md @@ -811,7 +811,7 @@ void f(1) Here, the first handler will catch exceptions of *Overflow* type and the second one - exceptions of *NumericError* type and all exceptions derived from it, including *Underflow* and *ZeroDivide*. -The handlers are checked in order of appearance, from the nearest to the most distant try block, until one matches the raise expression. For a try block, it would be a mistake to place a handler for a base exception type ahead of a handler for its derived type since that would ensure that the handler for the derived exception would never be invoked. +The handlers are checked in order of appearance, from the nearest to the try block to the most distant from it, until one matches the raise expression. For a try block, it would be a mistake to place a handler for a base exception type ahead of a handler for its derived type since that would ensure that the handler for the derived exception would never be invoked. ~~~~~ void f(1)