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 #197 from david-mitchell/patch-5

Browse Source 
Improve wording and structure of paragraph.
This commit is contained in:
Gabriel Dos Reis 2015-09-29 08:50:06 -07:00
commit 16a332330c
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
CppCoreGuidelines.md
View File

@ -1956,9 +1956,10 @@ such as passing a `const int&`, returning an `array<BigPOD>` by value, and retur
* Identify an array with a length specified separately * Identify an array with a length specified separately
* Identify a location in an array * Identify a location in an array
Confusion about what meaning a `T*` is the source of many serious errors, so using separate names for pointers of these separate uses makes code clearer. Using separate names for each of these uses improves code quality because confusion about the meaning of any particular `T*` is the source of many serious errors.
For debugging, `owner<T*>` and `not_null<T>` can be instrumented to check.
For example, `not_null<T*>` makes it obvious to a reader (human or machine) that a test for `nullptr` is not necessary before dereference. For example, `not_null<T*>` makes it obvious to a reader (human or machine) that a test for `nullptr` is not necessary before dereference.
Additionally, when debugging, `owner<T*>` and `not_null<T>` can be instrumented to check for correctness.
**Example**: Consider **Example**: Consider