2018-12-03 12:37:58 -05:00
|
|
|
---
|
|
|
|
|
Language: Cpp
|
|
|
|
|
AccessModifierOffset: -2
|
|
|
|
|
AlignAfterOpenBracket: Align
|
2024-04-03 16:35:23 -04:00
|
|
|
AlignArrayOfStructures: None
|
|
|
|
|
AlignConsecutiveAssignments:
|
|
|
|
|
Enabled: true
|
|
|
|
|
AcrossEmptyLines: false
|
|
|
|
|
AcrossComments: false
|
|
|
|
|
AlignCompound: false
|
|
|
|
|
PadOperators: true
|
|
|
|
|
AlignConsecutiveBitFields:
|
|
|
|
|
Enabled: false
|
|
|
|
|
AcrossEmptyLines: false
|
|
|
|
|
AcrossComments: false
|
|
|
|
|
AlignCompound: false
|
|
|
|
|
PadOperators: false
|
|
|
|
|
AlignConsecutiveDeclarations:
|
|
|
|
|
Enabled: false
|
|
|
|
|
AcrossEmptyLines: false
|
|
|
|
|
AcrossComments: false
|
|
|
|
|
AlignCompound: false
|
|
|
|
|
PadOperators: false
|
|
|
|
|
AlignConsecutiveMacros:
|
|
|
|
|
Enabled: false
|
|
|
|
|
AcrossEmptyLines: false
|
|
|
|
|
AcrossComments: false
|
|
|
|
|
AlignCompound: false
|
|
|
|
|
PadOperators: false
|
2018-12-03 12:37:58 -05:00
|
|
|
AlignEscapedNewlines: Left
|
Code cleanup: Refactor to clean up formatting issues
Refactored the clamscan code that determines 'what to scan' in order
to clean up some very messy logic and also to get around a difference in
how vscode and clang-format handle formatting #ifdef blocks in the
middle of an else/if.
In addition to refactoring, there is a slight behavior improvement. With
this change, doing `clamscan blah -` will now scan `blah` and then also
scan `stdin`. You can even do `clamscan - blah` to now scan `stdin` and
then scan `blah`. Before, The `-` had to be the only "filename" argument
in order to scan from stdin.
In addition, added a bunch of extra empty lines or changing multi-line
function calls to single-line function calls in order to get around a
bug in clang-format with these two options do not playing nice together:
- AlignConsecutiveAssignments: true
- AlignAfterOpenBracket: true
AlignAfterOpenBracket is not taking account the spaces inserted by
AlignConsecutiveAssignments, so you end up with stuff like this:
```c
bleeblah = 1;
blah = function(arg1,
arg2,
arg3);
// ^--- these args 4-left from where they should be.
```
VSCode, meanwhile, somehow fixes this whitespace issue so code that is
correctly formatted by VSCode doesn't have this bug, meaning that:
1. The clang-format check in GH Actions fails.
2. We'd all have to stop using format-on-save in VSCode and accept the
bug if we wanted those GH Actions tests to pass.
Adding an empty line before variable assignments from multi-line
function calls evades the buggy behavior.
This commit should resolve the clang-format github action test failures,
for now.
2022-03-10 20:55:13 -08:00
|
|
|
AlignOperands: Align
|
2024-04-03 16:35:23 -04:00
|
|
|
AlignTrailingComments:
|
|
|
|
|
Kind: Always
|
|
|
|
|
OverEmptyLines: 0
|
2020-01-03 15:53:29 -05:00
|
|
|
AllowAllArgumentsOnNextLine: true
|
2018-12-03 12:37:58 -05:00
|
|
|
AllowAllParametersOfDeclarationOnNextLine: true
|
2021-04-08 19:16:11 -07:00
|
|
|
AllowShortBlocksOnASingleLine: Never
|
2018-12-03 12:37:58 -05:00
|
|
|
AllowShortCaseLabelsOnASingleLine: false
|
2024-04-03 16:35:23 -04:00
|
|
|
AllowShortEnumsOnASingleLine: true
|
2018-12-03 12:37:58 -05:00
|
|
|
AllowShortFunctionsOnASingleLine: Empty
|
2020-01-03 15:53:29 -05:00
|
|
|
AllowShortIfStatementsOnASingleLine: WithoutElse
|
2024-04-03 16:35:23 -04:00
|
|
|
AllowShortLambdasOnASingleLine: All
|
2018-12-03 12:37:58 -05:00
|
|
|
AllowShortLoopsOnASingleLine: true
|
|
|
|
|
AlwaysBreakAfterDefinitionReturnType: None
|
|
|
|
|
AlwaysBreakAfterReturnType: None
|
|
|
|
|
AlwaysBreakBeforeMultilineStrings: false
|
|
|
|
|
AlwaysBreakTemplateDeclarations: MultiLine
|
2024-04-03 16:35:23 -04:00
|
|
|
AttributeMacros:
|
|
|
|
|
- __capability
|
2018-12-03 12:37:58 -05:00
|
|
|
BinPackArguments: true
|
|
|
|
|
BinPackParameters: true
|
2024-04-03 16:35:23 -04:00
|
|
|
BitFieldColonSpacing: Both
|
2021-04-08 19:16:11 -07:00
|
|
|
BraceWrapping:
|
2020-01-03 15:53:29 -05:00
|
|
|
AfterCaseLabel: false
|
2018-12-03 12:37:58 -05:00
|
|
|
AfterClass: true
|
Code cleanup: Refactor to clean up formatting issues
Refactored the clamscan code that determines 'what to scan' in order
to clean up some very messy logic and also to get around a difference in
how vscode and clang-format handle formatting #ifdef blocks in the
middle of an else/if.
In addition to refactoring, there is a slight behavior improvement. With
this change, doing `clamscan blah -` will now scan `blah` and then also
scan `stdin`. You can even do `clamscan - blah` to now scan `stdin` and
then scan `blah`. Before, The `-` had to be the only "filename" argument
in order to scan from stdin.
In addition, added a bunch of extra empty lines or changing multi-line
function calls to single-line function calls in order to get around a
bug in clang-format with these two options do not playing nice together:
- AlignConsecutiveAssignments: true
- AlignAfterOpenBracket: true
AlignAfterOpenBracket is not taking account the spaces inserted by
AlignConsecutiveAssignments, so you end up with stuff like this:
```c
bleeblah = 1;
blah = function(arg1,
arg2,
arg3);
// ^--- these args 4-left from where they should be.
```
VSCode, meanwhile, somehow fixes this whitespace issue so code that is
correctly formatted by VSCode doesn't have this bug, meaning that:
1. The clang-format check in GH Actions fails.
2. We'd all have to stop using format-on-save in VSCode and accept the
bug if we wanted those GH Actions tests to pass.
Adding an empty line before variable assignments from multi-line
function calls evades the buggy behavior.
This commit should resolve the clang-format github action test failures,
for now.
2022-03-10 20:55:13 -08:00
|
|
|
AfterControlStatement: Never
|
2018-12-03 12:37:58 -05:00
|
|
|
AfterEnum: false
|
2024-04-03 16:35:23 -04:00
|
|
|
AfterExternBlock: false
|
2018-12-03 12:37:58 -05:00
|
|
|
AfterFunction: true
|
|
|
|
|
AfterNamespace: true
|
|
|
|
|
AfterObjCDeclaration: false
|
|
|
|
|
AfterStruct: false
|
|
|
|
|
AfterUnion: false
|
|
|
|
|
BeforeCatch: false
|
|
|
|
|
BeforeElse: false
|
Code cleanup: Refactor to clean up formatting issues
Refactored the clamscan code that determines 'what to scan' in order
to clean up some very messy logic and also to get around a difference in
how vscode and clang-format handle formatting #ifdef blocks in the
middle of an else/if.
In addition to refactoring, there is a slight behavior improvement. With
this change, doing `clamscan blah -` will now scan `blah` and then also
scan `stdin`. You can even do `clamscan - blah` to now scan `stdin` and
then scan `blah`. Before, The `-` had to be the only "filename" argument
in order to scan from stdin.
In addition, added a bunch of extra empty lines or changing multi-line
function calls to single-line function calls in order to get around a
bug in clang-format with these two options do not playing nice together:
- AlignConsecutiveAssignments: true
- AlignAfterOpenBracket: true
AlignAfterOpenBracket is not taking account the spaces inserted by
AlignConsecutiveAssignments, so you end up with stuff like this:
```c
bleeblah = 1;
blah = function(arg1,
arg2,
arg3);
// ^--- these args 4-left from where they should be.
```
VSCode, meanwhile, somehow fixes this whitespace issue so code that is
correctly formatted by VSCode doesn't have this bug, meaning that:
1. The clang-format check in GH Actions fails.
2. We'd all have to stop using format-on-save in VSCode and accept the
bug if we wanted those GH Actions tests to pass.
Adding an empty line before variable assignments from multi-line
function calls evades the buggy behavior.
This commit should resolve the clang-format github action test failures,
for now.
2022-03-10 20:55:13 -08:00
|
|
|
BeforeLambdaBody: false
|
|
|
|
|
BeforeWhile: false
|
2018-12-03 12:37:58 -05:00
|
|
|
IndentBraces: false
|
|
|
|
|
SplitEmptyFunction: true
|
|
|
|
|
SplitEmptyRecord: true
|
|
|
|
|
SplitEmptyNamespace: true
|
2024-04-03 16:35:23 -04:00
|
|
|
BreakAfterAttributes: Never
|
|
|
|
|
BreakAfterJavaFieldAnnotations: false
|
|
|
|
|
BreakArrays: true
|
2018-12-03 12:37:58 -05:00
|
|
|
BreakBeforeBinaryOperators: None
|
2024-04-03 16:35:23 -04:00
|
|
|
BreakBeforeConceptDeclarations: Always
|
2018-12-03 12:37:58 -05:00
|
|
|
BreakBeforeBraces: Linux
|
2024-04-03 16:35:23 -04:00
|
|
|
BreakBeforeInlineASMColon: OnlyMultiline
|
2018-12-03 12:37:58 -05:00
|
|
|
BreakBeforeTernaryOperators: true
|
|
|
|
|
BreakConstructorInitializers: BeforeColon
|
2024-04-03 16:35:23 -04:00
|
|
|
BreakInheritanceList: BeforeColon
|
2018-12-03 12:37:58 -05:00
|
|
|
BreakStringLiterals: true
|
|
|
|
|
ColumnLimit: 0
|
|
|
|
|
CommentPragmas: '^ IWYU pragma:'
|
|
|
|
|
CompactNamespaces: false
|
|
|
|
|
ConstructorInitializerIndentWidth: 4
|
|
|
|
|
ContinuationIndentWidth: 4
|
|
|
|
|
Cpp11BracedListStyle: true
|
|
|
|
|
DerivePointerAlignment: true
|
|
|
|
|
DisableFormat: false
|
2024-04-03 16:35:23 -04:00
|
|
|
EmptyLineAfterAccessModifier: Never
|
|
|
|
|
EmptyLineBeforeAccessModifier: LogicalBlock
|
2018-12-03 12:37:58 -05:00
|
|
|
ExperimentalAutoDetectBinPacking: false
|
|
|
|
|
FixNamespaceComments: true
|
2021-04-08 19:16:11 -07:00
|
|
|
ForEachMacros:
|
2018-12-03 12:37:58 -05:00
|
|
|
- foreach
|
|
|
|
|
- Q_FOREACH
|
|
|
|
|
- BOOST_FOREACH
|
2024-04-03 16:35:23 -04:00
|
|
|
IfMacros:
|
|
|
|
|
- KJ_IF_MAYBE
|
2018-12-03 12:37:58 -05:00
|
|
|
IncludeBlocks: Preserve
|
2021-04-08 19:16:11 -07:00
|
|
|
IncludeCategories:
|
2018-12-03 12:37:58 -05:00
|
|
|
- Regex: '^"(llvm|llvm-c|clang|clang-c)/'
|
|
|
|
|
Priority: 2
|
2021-04-08 19:16:11 -07:00
|
|
|
SortPriority: 0
|
2024-04-03 16:35:23 -04:00
|
|
|
CaseSensitive: false
|
2018-12-03 12:37:58 -05:00
|
|
|
- Regex: '^(<|"(gtest|gmock|isl|json)/)'
|
|
|
|
|
Priority: 3
|
2021-04-08 19:16:11 -07:00
|
|
|
SortPriority: 0
|
2024-04-03 16:35:23 -04:00
|
|
|
CaseSensitive: false
|
2018-12-03 12:37:58 -05:00
|
|
|
- Regex: '.*'
|
|
|
|
|
Priority: 1
|
2021-04-08 19:16:11 -07:00
|
|
|
SortPriority: 0
|
2024-04-03 16:35:23 -04:00
|
|
|
CaseSensitive: false
|
2018-12-03 12:37:58 -05:00
|
|
|
IncludeIsMainRegex: '(Test)?$'
|
2021-04-08 19:16:11 -07:00
|
|
|
IncludeIsMainSourceRegex: ''
|
2024-04-03 16:35:23 -04:00
|
|
|
IndentAccessModifiers: false
|
Code cleanup: Refactor to clean up formatting issues
Refactored the clamscan code that determines 'what to scan' in order
to clean up some very messy logic and also to get around a difference in
how vscode and clang-format handle formatting #ifdef blocks in the
middle of an else/if.
In addition to refactoring, there is a slight behavior improvement. With
this change, doing `clamscan blah -` will now scan `blah` and then also
scan `stdin`. You can even do `clamscan - blah` to now scan `stdin` and
then scan `blah`. Before, The `-` had to be the only "filename" argument
in order to scan from stdin.
In addition, added a bunch of extra empty lines or changing multi-line
function calls to single-line function calls in order to get around a
bug in clang-format with these two options do not playing nice together:
- AlignConsecutiveAssignments: true
- AlignAfterOpenBracket: true
AlignAfterOpenBracket is not taking account the spaces inserted by
AlignConsecutiveAssignments, so you end up with stuff like this:
```c
bleeblah = 1;
blah = function(arg1,
arg2,
arg3);
// ^--- these args 4-left from where they should be.
```
VSCode, meanwhile, somehow fixes this whitespace issue so code that is
correctly formatted by VSCode doesn't have this bug, meaning that:
1. The clang-format check in GH Actions fails.
2. We'd all have to stop using format-on-save in VSCode and accept the
bug if we wanted those GH Actions tests to pass.
Adding an empty line before variable assignments from multi-line
function calls evades the buggy behavior.
This commit should resolve the clang-format github action test failures,
for now.
2022-03-10 20:55:13 -08:00
|
|
|
IndentCaseBlocks: false
|
2024-04-03 16:35:23 -04:00
|
|
|
IndentCaseLabels: true
|
|
|
|
|
IndentExternBlock: AfterExternBlock
|
2021-04-08 19:16:11 -07:00
|
|
|
IndentGotoLabels: true
|
2018-12-03 12:37:58 -05:00
|
|
|
IndentPPDirectives: None
|
2024-04-03 16:35:23 -04:00
|
|
|
IndentRequiresClause: true
|
2018-12-03 12:37:58 -05:00
|
|
|
IndentWidth: 4
|
|
|
|
|
IndentWrappedFunctionNames: false
|
2024-04-03 16:35:23 -04:00
|
|
|
InsertBraces: false
|
|
|
|
|
InsertNewlineAtEOF: false
|
Code cleanup: Refactor to clean up formatting issues
Refactored the clamscan code that determines 'what to scan' in order
to clean up some very messy logic and also to get around a difference in
how vscode and clang-format handle formatting #ifdef blocks in the
middle of an else/if.
In addition to refactoring, there is a slight behavior improvement. With
this change, doing `clamscan blah -` will now scan `blah` and then also
scan `stdin`. You can even do `clamscan - blah` to now scan `stdin` and
then scan `blah`. Before, The `-` had to be the only "filename" argument
in order to scan from stdin.
In addition, added a bunch of extra empty lines or changing multi-line
function calls to single-line function calls in order to get around a
bug in clang-format with these two options do not playing nice together:
- AlignConsecutiveAssignments: true
- AlignAfterOpenBracket: true
AlignAfterOpenBracket is not taking account the spaces inserted by
AlignConsecutiveAssignments, so you end up with stuff like this:
```c
bleeblah = 1;
blah = function(arg1,
arg2,
arg3);
// ^--- these args 4-left from where they should be.
```
VSCode, meanwhile, somehow fixes this whitespace issue so code that is
correctly formatted by VSCode doesn't have this bug, meaning that:
1. The clang-format check in GH Actions fails.
2. We'd all have to stop using format-on-save in VSCode and accept the
bug if we wanted those GH Actions tests to pass.
Adding an empty line before variable assignments from multi-line
function calls evades the buggy behavior.
This commit should resolve the clang-format github action test failures,
for now.
2022-03-10 20:55:13 -08:00
|
|
|
InsertTrailingCommas: None
|
2024-04-03 16:35:23 -04:00
|
|
|
IntegerLiteralSeparator:
|
|
|
|
|
Binary: 0
|
|
|
|
|
BinaryMinDigits: 0
|
|
|
|
|
Decimal: 0
|
|
|
|
|
DecimalMinDigits: 0
|
|
|
|
|
Hex: 0
|
|
|
|
|
HexMinDigits: 0
|
2018-12-03 12:37:58 -05:00
|
|
|
JavaScriptQuotes: Leave
|
|
|
|
|
JavaScriptWrapImports: true
|
|
|
|
|
KeepEmptyLinesAtTheStartOfBlocks: true
|
2024-04-03 16:35:23 -04:00
|
|
|
LambdaBodyIndentation: Signature
|
|
|
|
|
LineEnding: DeriveLF
|
2018-12-03 12:37:58 -05:00
|
|
|
MacroBlockBegin: ''
|
|
|
|
|
MacroBlockEnd: ''
|
|
|
|
|
MaxEmptyLinesToKeep: 1
|
|
|
|
|
NamespaceIndentation: None
|
|
|
|
|
ObjCBinPackProtocolList: Auto
|
|
|
|
|
ObjCBlockIndentWidth: 2
|
Code cleanup: Refactor to clean up formatting issues
Refactored the clamscan code that determines 'what to scan' in order
to clean up some very messy logic and also to get around a difference in
how vscode and clang-format handle formatting #ifdef blocks in the
middle of an else/if.
In addition to refactoring, there is a slight behavior improvement. With
this change, doing `clamscan blah -` will now scan `blah` and then also
scan `stdin`. You can even do `clamscan - blah` to now scan `stdin` and
then scan `blah`. Before, The `-` had to be the only "filename" argument
in order to scan from stdin.
In addition, added a bunch of extra empty lines or changing multi-line
function calls to single-line function calls in order to get around a
bug in clang-format with these two options do not playing nice together:
- AlignConsecutiveAssignments: true
- AlignAfterOpenBracket: true
AlignAfterOpenBracket is not taking account the spaces inserted by
AlignConsecutiveAssignments, so you end up with stuff like this:
```c
bleeblah = 1;
blah = function(arg1,
arg2,
arg3);
// ^--- these args 4-left from where they should be.
```
VSCode, meanwhile, somehow fixes this whitespace issue so code that is
correctly formatted by VSCode doesn't have this bug, meaning that:
1. The clang-format check in GH Actions fails.
2. We'd all have to stop using format-on-save in VSCode and accept the
bug if we wanted those GH Actions tests to pass.
Adding an empty line before variable assignments from multi-line
function calls evades the buggy behavior.
This commit should resolve the clang-format github action test failures,
for now.
2022-03-10 20:55:13 -08:00
|
|
|
ObjCBreakBeforeNestedBlockParam: true
|
2018-12-03 12:37:58 -05:00
|
|
|
ObjCSpaceAfterProperty: false
|
|
|
|
|
ObjCSpaceBeforeProtocolList: true
|
2024-04-03 16:35:23 -04:00
|
|
|
PackConstructorInitializers: BinPack
|
2018-12-03 12:37:58 -05:00
|
|
|
PenaltyBreakAssignment: 2
|
|
|
|
|
PenaltyBreakBeforeFirstCallParameter: 19
|
|
|
|
|
PenaltyBreakComment: 300
|
|
|
|
|
PenaltyBreakFirstLessLess: 120
|
2024-04-03 16:35:23 -04:00
|
|
|
PenaltyBreakOpenParenthesis: 0
|
2018-12-03 12:37:58 -05:00
|
|
|
PenaltyBreakString: 1000
|
|
|
|
|
PenaltyBreakTemplateDeclaration: 10
|
|
|
|
|
PenaltyExcessCharacter: 1000000
|
2024-04-03 16:35:23 -04:00
|
|
|
PenaltyIndentedWhitespace: 0
|
2018-12-03 12:37:58 -05:00
|
|
|
PenaltyReturnTypeOnItsOwnLine: 60
|
|
|
|
|
PointerAlignment: Right
|
2024-04-03 16:35:23 -04:00
|
|
|
PPIndentWidth: -1
|
|
|
|
|
QualifierAlignment: Leave
|
|
|
|
|
ReferenceAlignment: Pointer
|
2018-12-03 12:37:58 -05:00
|
|
|
ReflowComments: true
|
2024-04-03 16:35:23 -04:00
|
|
|
RemoveBracesLLVM: false
|
|
|
|
|
RemoveSemicolon: false
|
|
|
|
|
RequiresClausePosition: OwnLine
|
|
|
|
|
RequiresExpressionIndentation: OuterScope
|
|
|
|
|
SeparateDefinitionBlocks: Leave
|
|
|
|
|
ShortNamespaceLines: 1
|
|
|
|
|
SortIncludes: Never
|
|
|
|
|
SortJavaStaticImport: Before
|
|
|
|
|
SortUsingDeclarations: LexicographicNumeric
|
2018-12-03 12:37:58 -05:00
|
|
|
SpaceAfterCStyleCast: false
|
2020-01-03 15:53:29 -05:00
|
|
|
SpaceAfterLogicalNot: false
|
2018-12-03 12:37:58 -05:00
|
|
|
SpaceAfterTemplateKeyword: true
|
2024-04-03 16:35:23 -04:00
|
|
|
SpaceAroundPointerQualifiers: Default
|
2018-12-03 12:37:58 -05:00
|
|
|
SpaceBeforeAssignmentOperators: true
|
2024-04-03 16:35:23 -04:00
|
|
|
SpaceBeforeCaseColon: false
|
2018-12-03 12:37:58 -05:00
|
|
|
SpaceBeforeCpp11BracedList: false
|
|
|
|
|
SpaceBeforeCtorInitializerColon: true
|
|
|
|
|
SpaceBeforeInheritanceColon: true
|
|
|
|
|
SpaceBeforeParens: ControlStatements
|
2024-04-03 16:35:23 -04:00
|
|
|
SpaceBeforeParensOptions:
|
|
|
|
|
AfterControlStatements: true
|
|
|
|
|
AfterForeachMacros: true
|
|
|
|
|
AfterFunctionDefinitionName: false
|
|
|
|
|
AfterFunctionDeclarationName: false
|
|
|
|
|
AfterIfMacros: true
|
|
|
|
|
AfterOverloadedOperator: false
|
|
|
|
|
AfterRequiresInClause: false
|
|
|
|
|
AfterRequiresInExpression: false
|
|
|
|
|
BeforeNonEmptyParentheses: false
|
2018-12-03 12:37:58 -05:00
|
|
|
SpaceBeforeRangeBasedForLoopColon: true
|
2024-04-03 16:35:23 -04:00
|
|
|
SpaceBeforeSquareBrackets: false
|
2021-04-08 19:16:11 -07:00
|
|
|
SpaceInEmptyBlock: false
|
2018-12-03 12:37:58 -05:00
|
|
|
SpaceInEmptyParentheses: false
|
|
|
|
|
SpacesBeforeTrailingComments: 1
|
2024-04-03 16:35:23 -04:00
|
|
|
SpacesInAngles: Never
|
2021-04-08 19:16:11 -07:00
|
|
|
SpacesInConditionalStatement: false
|
2018-12-03 12:37:58 -05:00
|
|
|
SpacesInContainerLiterals: true
|
|
|
|
|
SpacesInCStyleCastParentheses: false
|
2024-04-03 16:35:23 -04:00
|
|
|
SpacesInLineCommentPrefix:
|
|
|
|
|
Minimum: 1
|
|
|
|
|
Maximum: -1
|
2018-12-03 12:37:58 -05:00
|
|
|
SpacesInParentheses: false
|
|
|
|
|
SpacesInSquareBrackets: false
|
2021-04-08 19:16:11 -07:00
|
|
|
Standard: Latest
|
2024-04-03 16:35:23 -04:00
|
|
|
StatementAttributeLikeMacros:
|
|
|
|
|
- Q_EMIT
|
2021-04-08 19:16:11 -07:00
|
|
|
StatementMacros:
|
2019-06-16 21:16:16 -04:00
|
|
|
- Q_UNUSED
|
|
|
|
|
- QT_REQUIRE_VERSION
|
2018-12-03 12:37:58 -05:00
|
|
|
TabWidth: 8
|
|
|
|
|
UseTab: Never
|
Code cleanup: Refactor to clean up formatting issues
Refactored the clamscan code that determines 'what to scan' in order
to clean up some very messy logic and also to get around a difference in
how vscode and clang-format handle formatting #ifdef blocks in the
middle of an else/if.
In addition to refactoring, there is a slight behavior improvement. With
this change, doing `clamscan blah -` will now scan `blah` and then also
scan `stdin`. You can even do `clamscan - blah` to now scan `stdin` and
then scan `blah`. Before, The `-` had to be the only "filename" argument
in order to scan from stdin.
In addition, added a bunch of extra empty lines or changing multi-line
function calls to single-line function calls in order to get around a
bug in clang-format with these two options do not playing nice together:
- AlignConsecutiveAssignments: true
- AlignAfterOpenBracket: true
AlignAfterOpenBracket is not taking account the spaces inserted by
AlignConsecutiveAssignments, so you end up with stuff like this:
```c
bleeblah = 1;
blah = function(arg1,
arg2,
arg3);
// ^--- these args 4-left from where they should be.
```
VSCode, meanwhile, somehow fixes this whitespace issue so code that is
correctly formatted by VSCode doesn't have this bug, meaning that:
1. The clang-format check in GH Actions fails.
2. We'd all have to stop using format-on-save in VSCode and accept the
bug if we wanted those GH Actions tests to pass.
Adding an empty line before variable assignments from multi-line
function calls evades the buggy behavior.
This commit should resolve the clang-format github action test failures,
for now.
2022-03-10 20:55:13 -08:00
|
|
|
WhitespaceSensitiveMacros:
|
|
|
|
|
- BOOST_PP_STRINGIZE
|
2024-04-03 16:35:23 -04:00
|
|
|
- CF_SWIFT_NAME
|
|
|
|
|
- NS_SWIFT_NAME
|
|
|
|
|
- PP_STRINGIZE
|
|
|
|
|
- STRINGIZE
|
2018-12-03 12:37:58 -05:00
|
|
|
...
|
|
|
|
|
|