Lines Matching +full:- +full:- +full:long +full:- +full:file +full:- +full:names

12 Before you upload code to Gerrit, use `git cl format` to auto-format your code.
18 *   {DEV} #define guards should be of the form: `<PATH>_<FILE>_H_`. (Compiler
19     codebase is varied, including `<PROJECT>_` makes the names excessively
20     long).
39 …tures guide](https://chromium.googlesource.com/chromium/src/+/main/styleguide/c++/c++-features.md).
43 #### File Names
46     If the file is an implementation of a class, the filename may be capitalized
51 #### Directory Names
52 *   Directory names should be all lowercase, unless following an externally
55 #### Variable Names
60 * Class and type names: start with capital letter and use CamelCase.
64 * {DEV} Variable names: start with lower case and use CamelCase (chosen for consistency)
65 * {DEV} Function names: Member functions start with lower case and use CamelCase. Non-member and st…
68 * Namespaces: short names. use all lower case
69 * {DEV} Enum Names: use strongly typed class enums when possible. Use CamelCase for class enum memb…
78 *   Each file **must** start with the following boilerplate notice:
83 //  Use of this source code is governed by a BSD-style license that can be
84 //  found in the LICENSE file.
88 * $YEAR should be set to the current year at the time a file is created, and not changed thereafter.
92 *   {DEV} Avoid excessively long lines. Please keep lines under 100 columns
93     long.
94 *   Use unix-style newlines.
96     spaces when you hit the TAB-key.
101     4-space indent from the outer scope for declarations/definitions.
106     header file where the whole function declaration and definition fit on one
154 *   If modifying pre-existing code that does not match the standard, the altered
170 Storing generated sources in the repository makes integration easier for non-GN
171 users. Python scripts can be expensive and slow to run at compile-time.