platform_system_core/.clang-format-4

BasedOnStyle: Google
AccessModifierOffset: -2
AllowShortFunctionsOnASingleLine: Inline
ColumnLimit: 100
CommentPragmas: NOLINT:.*
DerivePointerAlignment: false
IndentWidth: 4
PointerAlignment: Left
TabWidth: 4
UseTab: Never
PenaltyExcessCharacter: 32
Add a 2 width option of clang format. Make the default the 4 tab space version. Add a link to the 2 space version for libbacktrace. The only other difference between the 4 space and 2 space tab version is that the 2 space tab version allows short functions on a single line. This is for things like constructors, short destructors, or accessor functions. I believe this is closer to the Google C++ style guide. Bug: 36046320 Test: NA Change-Id: Ida08db18902eeb101f42869dd5590182529d54ef 2017-03-10 20:25:32 +01:00			`BasedOnStyle: Google`
			`AccessModifierOffset: -2`
Only allow short functions in class definitions. The previous rules would force short functions to be on a single line. This change only allows single function lines in class definitions. Test: Ran on a CL and verified single line functions only allowed in Test: class defintions. Change-Id: I5422543fdbb39da842bbd799c19fe2c443ff483c 2017-03-28 21:31:37 +02:00			`AllowShortFunctionsOnASingleLine: Inline`
Add a 2 width option of clang format. Make the default the 4 tab space version. Add a link to the 2 space version for libbacktrace. The only other difference between the 4 space and 2 space tab version is that the 2 space tab version allows short functions on a single line. This is for things like constructors, short destructors, or accessor functions. I believe this is closer to the Google C++ style guide. Bug: 36046320 Test: NA Change-Id: Ida08db18902eeb101f42869dd5590182529d54ef 2017-03-10 20:25:32 +01:00			`ColumnLimit: 100`
			`CommentPragmas: NOLINT:.*`
			`DerivePointerAlignment: false`
			`IndentWidth: 4`
			`PointerAlignment: Left`
			`TabWidth: 4`
			`UseTab: Never`
			`PenaltyExcessCharacter: 32`