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

idea for language feature xref

Browse Source
This commit is contained in:
Bjarne Stroustrup 2017-04-17 12:24:28 -04:00
parent 1b5f6d0c97
commit c46bebc58f
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
CppCoreGuidelines.md
View File

@ -66,7 +66,7 @@ or look at a specific language feature
* [`class`](#S-class)
* [constructor](#SS-ctor)
* [derived `class`](#SS-hier)
* [destructor](#SS-dtor)
* destructor: [and constructors](#Rc-matched), [when needed?] (#Rc-dtor), [may not fail](#Rc-dtor-fail)
* [exception](#S-errors)
* [`for`](#S-???)
* [`inline`](#S-class)
@ -75,7 +75,7 @@ or look at a specific language feature
* [operator](#S-???)
* [`public`, `private`, and `protected`](#S-???)
* [`static_assert`](#S-???)
* [`struct`](#S-class)
* `struct`: is a class with members public by default, [use if no invariant](#Rc-struct), [no private members](#Rc-class)
* [`template`](#S-???)
* [`unsigned`](#S-???)
* [`virtual`](#SS-hier)
@ -3651,7 +3651,8 @@ Subsections:
##### Reason
Ease of comprehension. If data is related (for fundamental reasons), that fact should be reflected in code.
Ease of comprehension.
If data is related (for fundamental reasons), that fact should be reflected in code.
##### Example