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

#included instead of #included

Browse Source
This commit is contained in:
Bledson Kivy 2017-06-01 23:26:45 -03:00 committed by GitHub
parent c7733a398a
commit d240b7611e
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CppCoreGuidelines.md
View File

@ -17729,7 +17729,7 @@ Source file rule summary:
* [SF.7: Don't write `using namespace` in a header file](#Rs-using-directive)
* [SF.8: Use `#include` guards for all `.h` files](#Rs-guards)
* [SF.9: Avoid cyclic dependencies among source files](#Rs-cycles)
* [SF.10: Avoid dependencies on implicitly `#included` names](#Rs-implicit)
* [SF.10: Avoid dependencies on implicitly `#include`d names](#Rs-implicit)
* [SF.20: Use `namespace`s to express logical structure](#Rs-namespace)
* [SF.21: Don't use an unnamed (anonymous) namespace in a header](#Rs-unnamed)
@ -18065,7 +18065,7 @@ Eliminate cycles; don't just break them with `#include` guards.
Flag all cycles.
### <a name="Rs-implicit"></a>SF.10: Avoid dependencies on implicitly `#included` names
### <a name="Rs-implicit"></a>SF.10: Avoid dependencies on implicitly `#include`d names
##### Reason
@ -18882,7 +18882,7 @@ Architectural rule summary:
A library is a collection of declarations and definitions maintained, documented, and shipped together.
A library could be a set of headers (a "header only library") or a set of headers plus a set of object files.
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 `#include`d
### <a name="Ra-dag"></a>A.4: There should be no cycles among libraries