There are coding style rules that are widely accepted by community, but newer were formalized in the document. Notable example is the question on how function arguments and parameters should be indented when they do not fit into one line.
This question was raised multiple times lately, mostly because of ongoing efforts to create Xen coding style formatting tool and because of new community members, who are not aware of such unwritten rules. Actually, this rule is already implicitly defined in the document by defining emacs coding style: 'c-file-style: "BSD"'. In this mode emacs lines up function arguments under the first argument. Naturally, most of Xen code is written in this style. So, lets state the obvious and fix this rule explicitly. Signed-off-by: Volodymyr Babchuk <volodymyr_babc...@epam.com> --- CODING_STYLE | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/CODING_STYLE b/CODING_STYLE index 6cc5b774cf..6479215a15 100644 --- a/CODING_STYLE +++ b/CODING_STYLE @@ -53,6 +53,20 @@ Line Length Lines should be less than 80 characters in length. Long lines should be split at sensible places and the trailing portions indented. +For multiline function declaration and call each new line should be +aligned with the first the parameter or argument. e.g.: + +void my_function_with_long_name(struct lengthy_struct_name *struct1, + struct lengthy_struct_name *struct2, + struct lengthy_struct_name *struct3); + +or + +function_with_so_many_params(wordy_parameter1, wordy_parameter2, + wordy_parameter3, wordy_parameter4); + +The same applies for macros. + User visible strings (e.g., printk() messages) should not be split so they can searched for more easily. -- 2.22.0 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
