From 64323c3827a948523e28612a2281b4f43da0aaa4 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Fri, 6 Nov 2020 09:21:31 +0100 Subject: eng: Move code formatting rules into one section Clarify the 80 character limit. Change the line continuation indent level. --- eng/coding-conventions.rst | 26 -------------------------- 1 file changed, 26 deletions(-) (limited to 'eng/coding-conventions.rst') diff --git a/eng/coding-conventions.rst b/eng/coding-conventions.rst index e34cd74..668a917 100644 --- a/eng/coding-conventions.rst +++ b/eng/coding-conventions.rst @@ -131,32 +131,6 @@ Language and Compiler * Do not use the register keyword. It is deprecated since C++14. -Formatting ------------ - -* Use spaces instead of tabs. -* Use two spaces for indentation, four spaces for - hanging indentation. -* Adhere to a limit of `80 characters per line `_.. -* Put function return types and names on one line if they fit. -* Put function calls on one line if they fit. -* No space between a function name or function-like macro and - the opening parens. -* Put braces on the same line as and one space after the - conditional expression ends. -* Put the opening brace of a function definition one line after - the closing parenthesis of its prototype. -* Put a single space inside and outside of each parenthesis - of a conditional expression. - * Exception: never put a space before a closing semi-colon. -* Put a single space before and after ternary operators. -* Put a single space before and after binary operators. -* Put no space between unary operators (e.g. *, &, !, ~, ++, --) - and their operands. -* No spaces around dereferencing operators (-> and .). -* Do not use more than one blank line in a row. -* Do not use trailing whitespace at the end of a line. - Readability ------------ -- cgit v1.2.3