2017-10-01 23:37:14 +00:00
|
|
|
# This file is an example configuration for clang-format 5.0.
|
|
|
|
#
|
|
|
|
# Note that this style definition should only be understood as a hint
|
|
|
|
# for writing new code. The rules are still work-in-progress and does
|
|
|
|
# not yet exactly match the style we have in the existing code.
|
2017-08-14 21:30:45 +00:00
|
|
|
|
|
|
|
# Use tabs whenever we need to fill whitespace that spans at least from one tab
|
|
|
|
# stop to the next one.
|
|
|
|
UseTab: Always
|
|
|
|
TabWidth: 8
|
|
|
|
IndentWidth: 8
|
|
|
|
ContinuationIndentWidth: 8
|
|
|
|
ColumnLimit: 80
|
|
|
|
|
|
|
|
# C Language specifics
|
|
|
|
Language: Cpp
|
|
|
|
|
|
|
|
# Align parameters on the open bracket
|
|
|
|
# someLongFunction(argument1,
|
|
|
|
# argument2);
|
|
|
|
AlignAfterOpenBracket: Align
|
|
|
|
|
|
|
|
# Don't align consecutive assignments
|
|
|
|
# int aaaa = 12;
|
|
|
|
# int b = 14;
|
|
|
|
AlignConsecutiveAssignments: false
|
|
|
|
|
|
|
|
# Don't align consecutive declarations
|
|
|
|
# int aaaa = 12;
|
|
|
|
# double b = 3.14;
|
|
|
|
AlignConsecutiveDeclarations: false
|
|
|
|
|
|
|
|
# Align escaped newlines as far left as possible
|
|
|
|
# #define A \
|
|
|
|
# int aaaa; \
|
|
|
|
# int b; \
|
|
|
|
# int cccccccc;
|
|
|
|
AlignEscapedNewlines: Left
|
|
|
|
|
|
|
|
# Align operands of binary and ternary expressions
|
|
|
|
# int aaa = bbbbbbbbbbb +
|
|
|
|
# cccccc;
|
|
|
|
AlignOperands: true
|
|
|
|
|
|
|
|
# Don't align trailing comments
|
|
|
|
# int a; // Comment a
|
|
|
|
# int b = 2; // Comment b
|
|
|
|
AlignTrailingComments: false
|
|
|
|
|
|
|
|
# By default don't allow putting parameters onto the next line
|
|
|
|
# myFunction(foo, bar, baz);
|
|
|
|
AllowAllParametersOfDeclarationOnNextLine: false
|
|
|
|
|
|
|
|
# Don't allow short braced statements to be on a single line
|
|
|
|
# if (a) not if (a) return;
|
|
|
|
# return;
|
|
|
|
AllowShortBlocksOnASingleLine: false
|
|
|
|
AllowShortCaseLabelsOnASingleLine: false
|
|
|
|
AllowShortFunctionsOnASingleLine: false
|
|
|
|
AllowShortIfStatementsOnASingleLine: false
|
|
|
|
AllowShortLoopsOnASingleLine: false
|
|
|
|
|
|
|
|
# By default don't add a line break after the return type of top-level functions
|
|
|
|
# int foo();
|
|
|
|
AlwaysBreakAfterReturnType: None
|
|
|
|
|
|
|
|
# Pack as many parameters or arguments onto the same line as possible
|
|
|
|
# int myFunction(int aaaaaaaaaaaa, int bbbbbbbb,
|
|
|
|
# int cccc);
|
|
|
|
BinPackArguments: true
|
|
|
|
BinPackParameters: true
|
|
|
|
|
|
|
|
# Attach braces to surrounding context except break before braces on function
|
|
|
|
# definitions.
|
|
|
|
# void foo()
|
|
|
|
# {
|
|
|
|
# if (true) {
|
|
|
|
# } else {
|
|
|
|
# }
|
|
|
|
# };
|
|
|
|
BreakBeforeBraces: Linux
|
|
|
|
|
|
|
|
# Break after operators
|
|
|
|
# int valuve = aaaaaaaaaaaaa +
|
|
|
|
# bbbbbb -
|
|
|
|
# ccccccccccc;
|
|
|
|
BreakBeforeBinaryOperators: None
|
|
|
|
BreakBeforeTernaryOperators: false
|
|
|
|
|
|
|
|
# Don't break string literals
|
|
|
|
BreakStringLiterals: false
|
|
|
|
|
|
|
|
# Use the same indentation level as for the switch statement.
|
|
|
|
# Switch statement body is always indented one level more than case labels.
|
|
|
|
IndentCaseLabels: false
|
|
|
|
|
|
|
|
# Don't indent a function definition or declaration if it is wrapped after the
|
|
|
|
# type
|
|
|
|
IndentWrappedFunctionNames: false
|
|
|
|
|
|
|
|
# Align pointer to the right
|
|
|
|
# int *a;
|
|
|
|
PointerAlignment: Right
|
|
|
|
|
|
|
|
# Don't insert a space after a cast
|
|
|
|
# x = (int32)y; not x = (int32) y;
|
|
|
|
SpaceAfterCStyleCast: false
|
|
|
|
|
|
|
|
# Insert spaces before and after assignment operators
|
|
|
|
# int a = 5; not int a=5;
|
|
|
|
# a += 42; a+=42;
|
|
|
|
SpaceBeforeAssignmentOperators: true
|
|
|
|
|
|
|
|
# Put a space before opening parentheses only after control statement keywords.
|
|
|
|
# void f() {
|
|
|
|
# if (true) {
|
|
|
|
# f();
|
|
|
|
# }
|
|
|
|
# }
|
|
|
|
SpaceBeforeParens: ControlStatements
|
|
|
|
|
|
|
|
# Don't insert spaces inside empty '()'
|
|
|
|
SpaceInEmptyParentheses: false
|
|
|
|
|
|
|
|
# The number of spaces before trailing line comments (// - comments).
|
|
|
|
# This does not affect trailing block comments (/* - comments).
|
|
|
|
SpacesBeforeTrailingComments: 1
|
|
|
|
|
|
|
|
# Don't insert spaces in casts
|
|
|
|
# x = (int32) y; not x = ( int32 ) y;
|
|
|
|
SpacesInCStyleCastParentheses: false
|
|
|
|
|
|
|
|
# Don't insert spaces inside container literals
|
|
|
|
# var arr = [1, 2, 3]; not var arr = [ 1, 2, 3 ];
|
|
|
|
SpacesInContainerLiterals: false
|
|
|
|
|
|
|
|
# Don't insert spaces after '(' or before ')'
|
|
|
|
# f(arg); not f( arg );
|
|
|
|
SpacesInParentheses: false
|
|
|
|
|
|
|
|
# Don't insert spaces after '[' or before ']'
|
|
|
|
# int a[5]; not int a[ 5 ];
|
|
|
|
SpacesInSquareBrackets: false
|
|
|
|
|
|
|
|
# Insert a space after '{' and before '}' in struct initializers
|
|
|
|
Cpp11BracedListStyle: false
|
|
|
|
|
|
|
|
# A list of macros that should be interpreted as foreach loops instead of as
|
|
|
|
# function calls.
|
|
|
|
ForEachMacros: ['for_each_string_list_item']
|
|
|
|
|
|
|
|
# The maximum number of consecutive empty lines to keep.
|
|
|
|
MaxEmptyLinesToKeep: 1
|
|
|
|
|
|
|
|
# No empty line at the start of a block.
|
|
|
|
KeepEmptyLinesAtTheStartOfBlocks: false
|
|
|
|
|
|
|
|
# Penalties
|
|
|
|
# This decides what order things should be done if a line is too long
|
clang-format: adjust line break penalties
We really, really, really want to limit the columns to 80 per line: One
of the few consistent style comments on the Git mailing list is that the
lines should not have more than 80 columns/line (even if 79 columns/line
would make more sense, given that the code is frequently viewed as diff,
and diffs adding an extra character).
The penalty of 5 for excess characters is way too low to guarantee that,
though, as pointed out by Brandon Williams.
From the existing clang-format examples and documentation, it appears
that 100 is a penalty deemed appropriate for Stuff You Really Don't
Want, so let's assign that as the penalty for "excess characters", i.e.
overly long lines.
While at it, adjust the penalties further: we are actually not that keen
on preventing new line breaks within comments or string literals, so the
penalty of 100 seems awfully high.
Likewise, we are not all that adamant about keeping line breaks away
from assignment operators (a lot of Git's code breaks immediately after
the `=` character just to keep that 80 columns/line limit).
We do frown a little bit more about functions' return types being on
their own line than the penalty 0 would suggest, so this was adjusted,
too.
Finally, we do not particularly fancy breaking before the first parameter
in a call, but if it keeps the line shorter than 80 columns/line, that's
what we do, so lower the penalty for breaking before a call's first
parameter, but not quite as much as introducing new line breaks to
comments.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-09-29 18:26:44 +00:00
|
|
|
PenaltyBreakAssignment: 10
|
|
|
|
PenaltyBreakBeforeFirstCallParameter: 30
|
|
|
|
PenaltyBreakComment: 10
|
2017-08-14 21:30:45 +00:00
|
|
|
PenaltyBreakFirstLessLess: 0
|
clang-format: adjust line break penalties
We really, really, really want to limit the columns to 80 per line: One
of the few consistent style comments on the Git mailing list is that the
lines should not have more than 80 columns/line (even if 79 columns/line
would make more sense, given that the code is frequently viewed as diff,
and diffs adding an extra character).
The penalty of 5 for excess characters is way too low to guarantee that,
though, as pointed out by Brandon Williams.
From the existing clang-format examples and documentation, it appears
that 100 is a penalty deemed appropriate for Stuff You Really Don't
Want, so let's assign that as the penalty for "excess characters", i.e.
overly long lines.
While at it, adjust the penalties further: we are actually not that keen
on preventing new line breaks within comments or string literals, so the
penalty of 100 seems awfully high.
Likewise, we are not all that adamant about keeping line breaks away
from assignment operators (a lot of Git's code breaks immediately after
the `=` character just to keep that 80 columns/line limit).
We do frown a little bit more about functions' return types being on
their own line than the penalty 0 would suggest, so this was adjusted,
too.
Finally, we do not particularly fancy breaking before the first parameter
in a call, but if it keeps the line shorter than 80 columns/line, that's
what we do, so lower the penalty for breaking before a call's first
parameter, but not quite as much as introducing new line breaks to
comments.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-09-29 18:26:44 +00:00
|
|
|
PenaltyBreakString: 10
|
|
|
|
PenaltyExcessCharacter: 100
|
2018-01-24 11:11:54 +00:00
|
|
|
PenaltyReturnTypeOnItsOwnLine: 60
|
2017-08-14 21:30:45 +00:00
|
|
|
|
|
|
|
# Don't sort #include's
|
|
|
|
SortIncludes: false
|