From 35e06007b5ec69a7b04f97ac3474e6efa15c07dd Mon Sep 17 00:00:00 2001 From: Jason Self Date: Sun, 14 Jan 2018 12:39:18 -0800 Subject: [PATCH] Update coding style Remove -nut because is not specified as being part of the source code style. Add -nprsa, -saf, -sai and -saw because they are mentioned in the Indent manual as being part of the source code style. The GNU Coding Standards don't mention it in the list of options but I tested Indent and verified it does this. Signed-off-by: Jason Self --- CONTRIBUTING.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e4d7a59..a74571f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -111,7 +111,6 @@ be used to style your code appropriately. A summary of the options corresponding to that style are: -l79 Set maximum line length for non-comment lines to 79. - -nut Use spaces instead of tabs. -bap Enter a blank lines after function bodies. -bbo Break long lines before boolean operators. -bl Put braces on line after if, etc. @@ -131,10 +130,14 @@ corresponding to that style are: -ndj Comments after declarations are treated the same as comments after other statements. -nfc1 Do not format comments in the first column as normal. -nfca Do not format any comments. + -nprs Do not put a space after every '(' and before every ')'. -nsc Do not put the ‘*’ character at the left of comments. -nsob Do not swallow optional blank lines. -pcs Insert a space between the name of the procedure being called and the ‘(’. -psl Put the type of a procedure on the line before its name. + -saf Put a space after each for. + -sai Put a space after each if. + -saw Put a space after each while. How to style your code is not the only thing covered in the GNU Coding Standards. Please consult the Standards for complete details. -- 2.31.1