From 614f5a041ea6e021c2ff9c4e462b0e22626c7f33 Mon Sep 17 00:00:00 2001 From: Uri Simchoni Date: Sat, 10 Mar 2018 07:08:28 +0200 Subject: [PATCH] README.Coding: codify line splitting on function calls Signed-off-by: Uri Simchoni Reviewed-by: Jeremy Allison Autobuild-User(master): Jeremy Allison Autobuild-Date(master): Tue Mar 13 01:48:21 CET 2018 on sn-devel-144 --- README.Coding | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.Coding b/README.Coding index e89925cad26..054cf3f1079 100644 --- a/README.Coding +++ b/README.Coding @@ -99,6 +99,7 @@ BreakBeforeBraces: Linux AllowShortIfStatementsOnASingleLine: false IndentCaseLabels: false BinPackParameters: false +BinPackArguments: false ========================= @@ -201,8 +202,8 @@ parameters across lines and not as encourage for gratuitous line splitting. Never split a line before columns 70 - 79 unless you have a really good reason. Be smart about formatting. -One exception to the previous rule is function declarations and -definitions. In function declarations and definitions, either the +One exception to the previous rule is function calls, declarations, and +definitions. In function calls, declarations, and definitions, either the declaration is a one-liner, or each parameter is listed on its own line. The rationale is that if there are many parameters, each one should be on its own line to make tracking interface changes easier. -- 2.11.4.GIT