From 11cc4c4775c9cb2d6849559ad61e9923a46c61a2 Mon Sep 17 00:00:00 2001 From: Sergey Zubkov Date: Wed, 5 Jan 2022 10:03:44 -0500 Subject: [PATCH] E.15: typo in title --- CppCoreGuidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 9e947e1..8482c69 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -15618,7 +15618,7 @@ Error-handling rule summary: * [E.12: Use `noexcept` when exiting a function because of a `throw` is impossible or unacceptable](#Re-noexcept) * [E.13: Never throw while being the direct owner of an object](#Re-never-throw) * [E.14: Use purpose-designed user-defined types as exceptions (not built-in types)](#Re-exception-types) -* [E.15: Throw by value, catch exceptions from a hierarchy reference](#Re-exception-ref) +* [E.15: Throw by value, catch exceptions from a hierarchy by reference](#Re-exception-ref) * [E.16: Destructors, deallocation, and `swap` must never fail](#Re-never-fail) * [E.17: Don't try to catch every exception in every function](#Re-not-always) * [E.18: Minimize the use of explicit `try`/`catch`](#Re-catch) @@ -16067,7 +16067,7 @@ The standard-library classes derived from `exception` should be used only as bas Catch `throw` and `catch` of a built-in type. Maybe warn about `throw` and `catch` using a standard-library `exception` type. Obviously, exceptions derived from the `std::exception` hierarchy are fine. -### E.15: Throw by value, catch exceptions from a hierarchy reference +### E.15: Throw by value, catch exceptions from a hierarchy by reference ##### Reason -- 2.11.4.GIT