From 149a68118826c8e35007416f1d53a48a8adfdbc1 Mon Sep 17 00:00:00 2001 From: Gabriel Dos Reis Date: Fri, 2 Oct 2015 03:31:10 -0700 Subject: [PATCH] Fix forward links in NL Fix #241. --- CppCoreGuidelines.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 7652c7a..6906160 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -12288,9 +12288,9 @@ Naming and layout rules: * [NL.3: Keep comments crisp](#Rl-comments-crisp) * [NL.4: Maintain a consistent indentation style](#Rl-indent) * [NL.5: Don't encode type information in names](#Rl-name-type) -* [NL.6: Make the length of a name roughly proportional to the length of its scope](#Rl-name-length) -* [NL.7: Use a consistent naming style](#Rl-name) -* [NL 9: Use ALL_CAPS for macro names only](#Rl-space) +* [NL.7: Make the length of a name roughly proportional to the length of its scope](#Rl-name-length) +* [NL.8: Use a consistent naming style](#Rl-name) +* [NL 9: Use ALL_CAPS for macro names only](#Rl-all-caps) * [NL.10: Avoid CamelCase](#Rl-camel) * [NL.15: Use spaces sparingly](#Rl-space) * [NL.16: Use a conventional class member declaration order](#Rl-order) @@ -12461,7 +12461,7 @@ Try to be consistent in your use of acronyms, lengths of identifiers: Would be possible except for the use of libraries with varying conventions. -### NL 9: Use ALL_CAPS for macro names only +### NL 9: Use ALL_CAPS for macro names only ##### Reason