StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Merge pull request #802 from severinmeyer/E-Typos-squashed

Browse Source 
Fix typos in section E: Error handling
This commit is contained in:
Gabriel Dos Reis 2016-11-22 07:52:01 -08:00 committed by GitHub
commit 783ab6c6ca
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CppCoreGuidelines.md
View File

@ -12860,7 +12860,7 @@ If `use()` could handle the failure to construct `bar` it can take control using
In either case, `Foo`'s constructor correctly destroys constructed members before passing control to whatever tried to create a `Foo`. In either case, `Foo`'s constructor correctly destroys constructed members before passing control to whatever tried to create a `Foo`.
Note that there is no return value that could contain an error code. Note that there is no return value that could contain an error code.
The `File_handle` constructor might defined like this: The `File_handle` constructor might be defined like this:
File_handle::File_handle(const string& name, const string& mode) File_handle::File_handle(const string& name, const string& mode)
:f{fopen(name.c_str(), mode.c_str())} :f{fopen(name.c_str(), mode.c_str())}
@ -13435,9 +13435,9 @@ In the absence of appropriate time estimation tools, this is hard to guarantee f
Such systems (e.g. flight control software) typically also ban the use of dynamic (heap) memory. Such systems (e.g. flight control software) typically also ban the use of dynamic (heap) memory.
So, the primary guideline for error handling is "use exceptions and [RAII](#Re-raii)." So, the primary guideline for error handling is "use exceptions and [RAII](#Re-raii)."
This section deals with the cases where you either do not have an efficient implementation or exceptions This section deals with the cases where you either do not have an efficient implementation of exceptions,
or have such a rat's nest of old-style code or have such a rat's nest of old-style code
(e.g., lots of pointers, ill-defined ownership, and lots of unsystematic error handling based on tests of errors codes) (e.g., lots of pointers, ill-defined ownership, and lots of unsystematic error handling based on tests of error codes)
that it is infeasible to introduce simple and systematic exception handling. that it is infeasible to introduce simple and systematic exception handling.
Before condemning exceptions or complaining too much about their cost, consider examples of the use of [error codes](#Re-no-throw-codes). Before condemning exceptions or complaining too much about their cost, consider examples of the use of [error codes](#Re-no-throw-codes).
@ -13465,7 +13465,7 @@ If we cannot throw an exception, we can simulate this RAII style of resource han
return 0; // zero indicates "good" return 0; // zero indicates "good"
} }
The problem is of course that the caller now have to remember to test the return value. The problem is of course that the caller now has to remember to test the return value.
**See also**: [Discussion](#Sd-???). **See also**: [Discussion](#Sd-???).