Lines Matching +refs:clang +refs:format +refs:style

23 or csv format) to identify related checks that may be implemented simultaneously.
49 * Please read and adhere to the style and process [guidelines ](#coding-conventions-and-formatting)…
57 * Use the **[Google style guide](https://google.github.io/styleguide/cppguide.html)** for source co…
58 …* The column limit is 132 (as opposed to the default value 80). The clang-format tool will handle …
59 …* The indent is 4 spaces instead of the default 2 spaces. Again, the clang-format tool will handle…
62 a good reason is "This violates the style guide, but it improves type safety."
64 * Run **clang-format** on your changes to maintain consistent formatting
65     * There are `.clang-format` files present in the repository to define clang-format settings
66       which are found and used automatically by clang-format.
67 …* **clang-format** binaries are available from the LLVM orginization, here: [LLVM](https://clang.l…
68 …currently uses clang-format version 5.0.0 to check that the lines of code you have changed are for…
69 	  recommended that you use the same version to format your code prior to submission.
74 >        $ git clang-format --style=file
75 >        # Check to see if clang-format made any changes and if they are OK.
146 * When editing configuration files for CMake, follow the style conventions of the surrounding code.
151 * The format is defined by
152   [cmake-format](https://github.com/cheshirekow/cmake_format)
153   using the `.cmake-format.py` file in the repository to define the settings.
154   See the cmake-format page for information about its simple markup for comments.
158   `# cmake-format: off` and `# cmake-format: on` comment lines.
160 * To run: `cmake-format --in-place $FILENAME`
161 * **IMPORTANT (June 2018)** cmake-format v0.3.6 has a
164   A workaround is to use the following command _before_ running cmake-format:
175 any new files need to have the Khronos license (Apache 2.0 style) and copyright included.