-
Notifications
You must be signed in to change notification settings - Fork 32
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
23931b8
commit 48e5143
Showing
14 changed files
with
1,091 additions
and
1,012 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,94 @@ | ||
# Copyright (C) 2016 Olivier Goffart <[email protected]> | ||
# | ||
# You may use this file under the terms of the 3-clause BSD license. | ||
# See the file LICENSE from this package for details. | ||
|
||
# This is the clang-format configuration style to be used by Qt, | ||
# based on the rules from https://wiki.qt.io/Qt_Coding_Style and | ||
# https://wiki.qt.io/Coding_Conventions | ||
|
||
--- | ||
# Webkit style was loosely based on the Qt style | ||
BasedOnStyle: WebKit | ||
|
||
Standard: Cpp11 | ||
|
||
# Leave the line breaks up to the user. | ||
# Note that this may be changed at some point in the future. | ||
ColumnLimit: 0 | ||
# How much weight do extra characters after the line length limit have. | ||
# PenaltyExcessCharacter: 4 | ||
|
||
# Disable reflow of qdoc comments: indentation rules are different. | ||
# Translation comments are also excluded. | ||
CommentPragmas: "^!|^:" | ||
|
||
# We want a space between the type and the star for pointer types. | ||
PointerBindsToType: false | ||
|
||
# We use template< without space. | ||
SpaceAfterTemplateKeyword: false | ||
|
||
# We want to break before the operators, but not before a '='. | ||
BreakBeforeBinaryOperators: All | ||
|
||
# Braces are usually attached, but not after functions or class declarations. | ||
BreakBeforeBraces: Custom | ||
BraceWrapping: | ||
AfterClass: true | ||
AfterControlStatement: true | ||
AfterEnum: true | ||
AfterFunction: true | ||
AfterNamespace: true | ||
AfterObjCDeclaration: true | ||
AfterStruct: true | ||
AfterUnion: true | ||
BeforeCatch: true | ||
BeforeElse: true | ||
IndentBraces: false | ||
|
||
BreakBeforeTernaryOperators: true | ||
|
||
BreakConstructorInitializers: BeforeComma | ||
|
||
# Indent initializers by 3 spaces | ||
ConstructorInitializerIndentWidth: 3 | ||
|
||
# No indentation for namespaces. | ||
NamespaceIndentation: None | ||
|
||
# Horizontally align arguments after an open bracket. | ||
# The coding style does not specify the following, but this is what gives | ||
# results closest to the existing code. | ||
AlignAfterOpenBracket: true | ||
AlwaysBreakTemplateDeclarations: true | ||
|
||
# Ideally we should also allow less short function in a single line, but | ||
# clang-format does not handle that. | ||
AllowShortFunctionsOnASingleLine: Inline | ||
|
||
# The coding style specifies some include order categories, but also tells to | ||
# separate categories with an empty line. It does not specify the order within | ||
# the categories. Since the SortInclude feature of clang-format does not | ||
# re-order includes separated by empty lines, the feature is not used. | ||
SortIncludes: false | ||
|
||
# macros for which the opening brace stays attached. | ||
ForEachMacros: [ foreach, Q_FOREACH, BOOST_FOREACH, forever, Q_FOREVER, QBENCHMARK, QBENCHMARK_ONCE ] | ||
|
||
IndentCaseLabels: true | ||
|
||
IndentPPDirectives: AfterHash | ||
|
||
AlignAfterOpenBracket: Align | ||
|
||
AccessModifierOffset: -3 | ||
|
||
IndentWidth: 3 | ||
|
||
#StatementMacros ['Q_OBJECT', 'Q_UNUSED'] | ||
|
||
ColumnLimit: 120 | ||
|
||
|
||
|
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.