You are (never) stuck with someone else's coding style -- you can always reformat C/C++ source code into a format that works for you.
There used to be a GNU tool that reformatted existing C/C++ source code into different formats (that goes waaayyyy back in programming history) that did this - but I couldn't find that tool after a quick search. I am (pretty sure) that tool is still in the GNU tool set -- maybe they renamed it?
But CLANG has a tool (clang-format) which can be configured here: (Link: lang.llvm.org): ClangFormatStyleOptions
There are also settings for the major coding standards:
- LLVM - A style complying with the LLVM coding standards
- Google - A style complying with Google’s C++ style guide
- Chromium - A style complying with Chromium’s style guide
- Mozilla - A style complying with Mozilla’s style guide
- WebKit - A style complying with WebKit’s style guide
- Microsoft - A style complying with Microsoft’s style guide
- GNU - A style complying with the GNU coding standards
- InheritParentConfig - Not a real style, but allows to use the .clang-format file from theparent directory (or its parent if there is none). If there is no parentfile found it falls back to the fallback style, and applies the changesto that. With this option you can overwrite some parts of your main stylefor your subdirectories. This is also possible through the command line,e.g.:--={BasedOnStyle: InheritParentConfig, ColumnLimit: 20}
- InheritParentConfig=<directory-path> Same as the above except that the inheritance is redirected to <directory-path>. This is only supported in configuration files.
