|
| 1 | +#****************************************************************************** |
| 2 | +#* Copyright (c) 2025 Calypso Networks Association https://calypsonet.org/ * |
| 3 | +#* * |
| 4 | +#* See the NOTICE file(s) distributed with this work for additional * |
| 5 | +#* information regarding copyright ownership. * |
| 6 | +#* * |
| 7 | +#* This program and the accompanying materials are made available under the * |
| 8 | +#* terms of the Eclipse Public License 2.0 which is available at * |
| 9 | +#* http://www.eclipse.org/legal/epl-2.0 * |
| 10 | +#* * |
| 11 | +#* SPDX-License-Identifier: EPL-2.0 * |
| 12 | +#******************************************************************************/ |
| 13 | + |
| 14 | +#http://clang.llvm.org/docs/ClangFormatStyleOptions.html |
| 15 | + |
| 16 | +# The style used for all options not specifically set in the configuration. |
| 17 | +# This option is supported only in the clang-format configuration (both within |
| 18 | +# -style='{...}' and the .clang-format file). |
| 19 | +# LLVM A style complying with the LLVM coding standards |
| 20 | +# Google A style complying with Google’s C++ style guide |
| 21 | +# Chromium A style complying with Chromium’s style guide |
| 22 | +# Mozilla A style complying with Mozilla’s style guide |
| 23 | +# WebKit A style complying with WebKit’s style guide |
| 24 | +BasedOnStyle: Webkit |
| 25 | + |
| 26 | +# The extra indent or outdent of access modifiers, e.g. public:. |
| 27 | +AccessModifierOffset: -4 |
| 28 | + |
| 29 | +# If true, horizontally aligns arguments after an open bracket. |
| 30 | +# This applies to round brackets (parentheses), angle brackets and square |
| 31 | +# brackets. This will result in formattings like code |
| 32 | +# someLongFunction(argument1, argument2); endcode |
| 33 | +AlignAfterOpenBracket: AlwaysBreak |
| 34 | + |
| 35 | +# If true, aligns escaped newlines as far left as possible. Otherwise puts them |
| 36 | +# into the right-most column. |
| 37 | +#AlignEscapedNewlinesLeft |
| 38 | + |
| 39 | +# If true, horizontally align operands of binary and ternary expressions. |
| 40 | +AlignOperands: true |
| 41 | + |
| 42 | +# If true, aligns trailing comments. |
| 43 | +AlignTrailingComments: true |
| 44 | + |
| 45 | +# Allow putting all parameters of a function declaration onto the next line even |
| 46 | +# if BinPackParameters is false. |
| 47 | +AllowAllParametersOfDeclarationOnNextLine: true |
| 48 | + |
| 49 | +# Allows contracting simple braced statements to a single line. |
| 50 | +# E.g., this allows if (a) { return; } to be put on a single line. |
| 51 | +AllowShortBlocksOnASingleLine: false |
| 52 | + |
| 53 | +# If true, short case labels will be contracted to a single line. |
| 54 | +AllowShortCaseLabelsOnASingleLine: false |
| 55 | + |
| 56 | +# Dependent on the value, int f() { return 0; } can be put on a single line. |
| 57 | +# SFS_None (in configuration: None) Never merge functions into a single line. |
| 58 | +# SFS_Inline (in configuration: Inline) Only merge functions defined inside a |
| 59 | +# class. |
| 60 | +# SFS_Empty (in configuration: Empty) Only merge empty functions. |
| 61 | +# SFS_All (in configuration: All) Merge all functions fitting on a single line. |
| 62 | +AllowShortFunctionsOnASingleLine: None |
| 63 | + |
| 64 | +# If true, if (a) return; can be put on a single line. |
| 65 | +#AllowShortIfStatementsOnASingleLine: false |
| 66 | + |
| 67 | +# If true, while (true) continue; can be put on a single line. |
| 68 | +AllowShortLoopsOnASingleLine: true |
| 69 | + |
| 70 | +# If true, always break after function definition return types. |
| 71 | +# More truthfully called ‘break before the identifier following the type in a |
| 72 | +# function definition’. |
| 73 | +# PenaltyReturnTypeOnItsOwnLine becomes irrelevant. |
| 74 | +AlwaysBreakAfterDefinitionReturnType: All |
| 75 | + |
| 76 | +# If true, always break before multiline string literals. |
| 77 | +AlwaysBreakBeforeMultilineStrings: false |
| 78 | + |
| 79 | +# If true, always break after the template<...> of a template declaration. |
| 80 | +AlwaysBreakTemplateDeclarations: true |
| 81 | + |
| 82 | +# If false, a function call’s arguments will either be all on the same line or |
| 83 | +# will have one line each. |
| 84 | +BinPackArguments: false |
| 85 | + |
| 86 | +# If false, a function call’s arguments will either be all |
| 87 | +# on the same line or will have one line each. |
| 88 | +BinPackParameters: false |
| 89 | + |
| 90 | +# The way to wrap binary operators. |
| 91 | +# BOS_None (in configuration: None) Break after operators. |
| 92 | +# BOS_NonAssignment (in configuration: NonAssignment) Break before operators |
| 93 | +# that aren’t assignments. |
| 94 | +# BOS_All (in configuration: All) Break before operators. |
| 95 | +#BreakBeforeBinaryOperators: None |
| 96 | + |
| 97 | +# The brace breaking style to use. |
| 98 | +# BS_Attach (in configuration: Attach) Always attach braces to surrounding |
| 99 | +# context. |
| 100 | +# BS_Linux (in configuration: Linux) Like Attach, but break before braces on |
| 101 | +# function, namespace and class definitions. |
| 102 | +# BS_Stroustrup (in configuration: Stroustrup) Like Attach, but break before |
| 103 | +# function definitions, and ‘else’. |
| 104 | +# BS_Allman (in configuration: Allman) Always break before braces. |
| 105 | +# BS_GNU (in configuration: GNU) Always break before braces and add an extra |
| 106 | +# level of indentation to braces of control statements, not to those of class, |
| 107 | +# function or other definitions. |
| 108 | +BreakBeforeBraces: WebKit |
| 109 | + |
| 110 | +# If true, ternary operators will be placed after line breaks. |
| 111 | +BreakBeforeTernaryOperators: true |
| 112 | + |
| 113 | +# Always break constructor initializers before commas and align the commas with |
| 114 | +# the colon. |
| 115 | +BreakConstructorInitializersBeforeComma: true |
| 116 | + |
| 117 | +# The column limit. |
| 118 | +# A column limit of 0 means that there is no column limit. In this case, |
| 119 | +# clang-format will respect the input’s line breaking decisions within |
| 120 | +# statements unless they contradict other rules. |
| 121 | +ColumnLimit: 80 |
| 122 | + |
| 123 | +# A regular expression that describes comments with special meaning, which |
| 124 | +# should not be split into lines or otherwise changed. |
| 125 | +CommentPragmas: "\/*(.*)*\/" |
| 126 | + |
| 127 | +# If the constructor initializers don’t fit on a line, put each initializer on |
| 128 | +# its own line. |
| 129 | +#ConstructorInitializerAllOnOneLineOrOnePerLine: false |
| 130 | + |
| 131 | +# The number of characters to use for indentation of constructor initializer |
| 132 | +# lists. |
| 133 | +ConstructorInitializerIndentWidth: 0 |
| 134 | + |
| 135 | +# Indent width for line continuations. |
| 136 | +#ContinuationIndentWidth: 4 |
| 137 | + |
| 138 | +# If true, format braced lists as best suited for C++11 braced lists. |
| 139 | +# Important differences: - No spaces inside the braced list. - No line break |
| 140 | +# before the closing brace. - Indentation with the continuation indent, not with |
| 141 | +# the block indent. |
| 142 | +# Fundamentally, C++11 braced lists are formatted exactly like function calls |
| 143 | +# would be formatted in their place. If the braced list follows a name (e.g. a |
| 144 | +# type or variable name), clang-format formats as if the {} were the parentheses |
| 145 | +# of a function call with that name. If there is no name, a zero-length name is |
| 146 | +# assumed. |
| 147 | +Cpp11BracedListStyle: true |
| 148 | + |
| 149 | +# If true, analyze the formatted file for the most common alignment of & and *. |
| 150 | +# Point |
| 151 | +#DerivePointerAlignment: false |
| 152 | + |
| 153 | +# Disables formatting at all. |
| 154 | +#DisableFormat: false |
| 155 | + |
| 156 | +# If true, clang-format detects whether function calls and definitions are |
| 157 | +# formatted with one parameter per line. |
| 158 | +# Each call can be bin-packed, one-per-line or inconclusive. If it is |
| 159 | +# inconclusive, e.g. completely on one line, but a decision needs to be made, |
| 160 | +# clang-format analyzes whether there are other bin-packed cases in the input |
| 161 | +# file and act accordingly. |
| 162 | +# NOTE: This is an experimental flag, that might go away or be renamed. Do not |
| 163 | +# use this in config files, etc. Use at your own risk. |
| 164 | +ExperimentalAutoDetectBinPacking: false |
| 165 | + |
| 166 | +# A vector of macros that should be interpreted as foreach loops instead of as |
| 167 | +# function calls. |
| 168 | +# These are expected to be macros of the form: code |
| 169 | +# FOREACH(<variable-declaration>, ...) <loop-body> endcode |
| 170 | +# For example: BOOST_FOREACH. |
| 171 | +#ForEachMacros (std::vector<std::string>) |
| 172 | + |
| 173 | +# Indent case labels one level from the switch statement. |
| 174 | +# When false, use the same indentation level as for the switch statement. Switch |
| 175 | +# statement body is always indented one level more than case labels. |
| 176 | +IndentCaseLabels: false |
| 177 | + |
| 178 | +# The number of columns to use for indentation. |
| 179 | +IndentWidth: 4 |
| 180 | + |
| 181 | +# Indent if a function definition or declaration is wrapped after the type. |
| 182 | +#IndentWrappedFunctionNames: false |
| 183 | + |
| 184 | +# If true, empty lines at the start of blocks are kept. |
| 185 | +KeepEmptyLinesAtTheStartOfBlocks: false |
| 186 | + |
| 187 | +# Language, this format style is targeted at. |
| 188 | +# LK_None (in configuration: None) Do not use. |
| 189 | +# LK_Cpp (in configuration: Cpp) Should be used for C, C++, ObjectiveC, |
| 190 | +# ObjectiveC++. |
| 191 | +# LK_Java (in configuration: Java) Should be used for Java. |
| 192 | +# LK_JavaScript (in configuration: JavaScript) Should be used for JavaScript. |
| 193 | +# LK_Proto (in configuration: Proto) Should be used for Protocol Buffers |
| 194 | +# (https://developers.google.com/protocol-buffers/). |
| 195 | +Language: Cpp |
| 196 | + |
| 197 | +# The maximum number of consecutive empty lines to keep. |
| 198 | +#MaxEmptyLinesToKeep: 0 |
| 199 | + |
| 200 | +# The indentation used for namespaces. |
| 201 | +# NI_None (in configuration: None) Don’t indent in namespaces. |
| 202 | +# NI_Inner (in configuration: Inner) Indent only in inner namespaces (nested in |
| 203 | +# other namespaces). |
| 204 | +# NI_All (in configuration: All) Indent in all namespaces. |
| 205 | +NamespaceIndentation: None |
| 206 | + |
| 207 | +# The number of characters to use for indentation of ObjC blocks. |
| 208 | +#ObjCBlockIndentWidth: 4 |
| 209 | + |
| 210 | +# Add a space after @property in Objective-C, i.e. use \@property (readonly) |
| 211 | +# instead of \@property(readonly). |
| 212 | +#ObjCSpaceAfterProperty: false |
| 213 | + |
| 214 | +# Add a space in front of an Objective-C protocol list, i.e. use Foo <Protocol> |
| 215 | +# instead of Foo<Protocol>. |
| 216 | +#ObjCSpaceBeforeProtocolList: false |
| 217 | + |
| 218 | +# The penalty for breaking a function call after “call(”. |
| 219 | +#PenaltyBreakBeforeFirstCallParameter (unsigned) |
| 220 | + |
| 221 | +# The penalty for each line break introduced inside a comment. |
| 222 | +#PenaltyBreakComment (unsigned) |
| 223 | + |
| 224 | +# The penalty for breaking before the first <<. |
| 225 | +#PenaltyBreakFirstLessLess (unsigned) |
| 226 | + |
| 227 | +# The penalty for each line break introduced inside a string literal. |
| 228 | +#PenaltyBreakString (unsigned) |
| 229 | + |
| 230 | +# The penalty for each character outside of the column limit. |
| 231 | +#PenaltyExcessCharacter (unsigned) |
| 232 | + |
| 233 | +# Penalty for putting the return type of a function onto its own line. |
| 234 | +#PenaltyReturnTypeOnItsOwnLine (unsigned) |
| 235 | + |
| 236 | +# If true, analyze the formatted file for the most common alignment of & and *. |
| 237 | +# PointerAlignment is then used only as fallback. |
| 238 | +PointerAlignment: Left |
| 239 | + |
| 240 | +# If true, a space may be inserted after C style casts. |
| 241 | +SpaceAfterCStyleCast: false |
| 242 | + |
| 243 | +# If false, spaces will be removed before assignment operators. |
| 244 | +SpaceBeforeAssignmentOperators: true |
| 245 | + |
| 246 | +# Defines in which cases to put a space before opening parentheses. |
| 247 | +# SBPO_Never (in configuration: Never) Never put a space before opening |
| 248 | +# parentheses. |
| 249 | +# SBPO_ControlStatements (in configuration: ControlStatements) Put a space |
| 250 | +# before opening parentheses only after control statement keywords |
| 251 | +# (for/if/while...). |
| 252 | +# SBPO_Always (in configuration: Always) Always put a space before opening |
| 253 | +# parentheses, except when it’s prohibited by the syntax rules (in function-like |
| 254 | +# macro definitions) or when determined by other style rules (after unary |
| 255 | +# operators, opening parentheses, etc.) |
| 256 | +SpaceBeforeParens: ControlStatements |
| 257 | + |
| 258 | +# If true, spaces may be inserted into ‘()’. |
| 259 | +SpaceInEmptyParentheses: false |
| 260 | + |
| 261 | +# The number of spaces before trailing line comments (// - comments). |
| 262 | +# This does not affect trailing block comments (/**/ - comments) as those |
| 263 | +# commonly have different usage patterns and a number of special cases. |
| 264 | +SpacesBeforeTrailingComments: 2 |
| 265 | + |
| 266 | +# If true, spaces will be inserted after ‘<’ and before ‘>’ in template argument |
| 267 | +# lists |
| 268 | +SpacesInAngles: false |
| 269 | + |
| 270 | +# If true, spaces may be inserted into C style casts. |
| 271 | +SpacesInCStyleCastParentheses: false |
| 272 | + |
| 273 | +# If true, spaces are inserted inside container literals (e.g. ObjC and |
| 274 | +# Javascript array and dict literals). |
| 275 | +SpacesInContainerLiterals: false |
| 276 | + |
| 277 | +# If true, spaces will be inserted after ‘(‘ and before ‘)’. |
| 278 | +SpacesInParentheses: false |
| 279 | + |
| 280 | +# If true, spaces will be inserted after ‘[‘ and before ‘]’. |
| 281 | +SpacesInSquareBrackets: false |
| 282 | + |
| 283 | +# Format compatible with this standard, e.g. use A<A<int> > instead of A<A<int>> |
| 284 | +# for LS_Cpp03. |
| 285 | +# LS_Cpp03 (in configuration: Cpp03) Use C++03-compatible syntax. |
| 286 | +# LS_Cpp11 (in configuration: Cpp11) Use features of C++11 (e.g. A<A<int>> |
| 287 | +# instead of A<A<int> >). |
| 288 | +# LS_Auto (in configuration: Auto) Automatic detection based on the input. |
| 289 | +Standard: Cpp11 |
| 290 | + |
| 291 | +# The number of columns used for tab stops. |
| 292 | +TabWidth: 4 |
| 293 | + |
| 294 | +# The way to use tab characters in the resulting file. |
| 295 | +# UT_Never (in configuration: Never) Never use tab. |
| 296 | +# UT_ForIndentation (in configuration: ForIndentation) Use tabs only for |
| 297 | +# indentation. |
| 298 | +# UT_Always (in configuration: Always) Use tabs whenever we need to fill |
| 299 | +# whitespace that spans at least from one tab stop to the next one. |
| 300 | +UseTab: Never |
| 301 | + |
| 302 | +# Indent code enclosed in an extern block |
| 303 | +IndentExternBlock: NoIndent |
0 commit comments