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

Fix various item tags (missing colons)

Browse Source 
I.2, C.10, A.1, A.2, A.4, NL.5
This commit is contained in:
galik 2017-05-25 23:09:08 +01:00
parent c721b2c325
commit fa50221dd0
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
CppCoreGuidelines.md
View File

@ -1257,7 +1257,7 @@ Functions can be template functions and sets of functions can be classes or clas
* (Simple) A function should not make control-flow decisions based on the values of variables declared at namespace scope. * (Simple) A function should not make control-flow decisions based on the values of variables declared at namespace scope.
* (Simple) A function should not write to variables declared at namespace scope. * (Simple) A function should not write to variables declared at namespace scope.
### <a name="Ri-global"></a>I.2 Avoid global variables ### <a name="Ri-global"></a>I.2: Avoid global variables
##### Reason ##### Reason
@ -4225,7 +4225,7 @@ Concrete type rule summary:
* [C.10: Prefer concrete types over class hierarchies](#Rc-concrete) * [C.10: Prefer concrete types over class hierarchies](#Rc-concrete)
* [C.11: Make concrete types regular](#Rc-regular) * [C.11: Make concrete types regular](#Rc-regular)
### <a name="Rc-concrete"></a>C.10 Prefer concrete types over class hierarchies ### <a name="Rc-concrete"></a>C.10: Prefer concrete types over class hierarchies
##### Reason ##### Reason
@ -18446,9 +18446,9 @@ This section contains ideas about higher-level architectural ideas and libraries
Architectural rule summary: Architectural rule summary:
* [A.1 Separate stable from less stable part of code](#Ra-stable) * [A.1: Separate stable from less stable part of code](#Ra-stable)
* [A.2 Express potentially reusable parts as a library](#Ra-lib) * [A.2: Express potentially reusable parts as a library](#Ra-lib)
* [A.4 There should be no cycles among libraries](#?Ra-dag) * [A.4: There should be no cycles among libraries](#?Ra-dag)
* [???](#???) * [???](#???)
* [???](#???) * [???](#???)
* [???](#???) * [???](#???)
@ -18456,11 +18456,11 @@ Architectural rule summary:
* [???](#???) * [???](#???)
* [???](#???) * [???](#???)
### <a name="Ra-stable"></a>A.1 Separate stable from less stable part of code ### <a name="Ra-stable"></a>A.1: Separate stable from less stable part of code
??? ???
### <a name="Ra-lib"></a>A.2 Express potentially reusable parts as a library ### <a name="Ra-lib"></a>A.2: Express potentially reusable parts as a library
##### Reason ##### Reason
@ -18471,7 +18471,7 @@ A library could be a set of headers (a "header only library") or a set of header
A library can be statically or dynamically linked into a program, or it may be `#included` A library can be statically or dynamically linked into a program, or it may be `#included`
### <a name="Ra-dag"></a>A.4 There should be no cycles among libraries ### <a name="Ra-dag"></a>A.4: There should be no cycles among libraries
##### Reason ##### Reason
@ -19729,7 +19729,7 @@ Always indenting the statement after `if (...)`, `for (...)`, and `while (...)`
Use a tool. Use a tool.
### <a name="Rl-name-type"></a>NL.5 Don't encode type information in names ### <a name="Rl-name-type"></a>NL.5: Don't encode type information in names
##### Rationale ##### Rationale