Lines Matching full:are

3 style followed by the Linux kernel. Naturally there are exceptions. Most
10 that GCC specific extensions are generally accepted. The code must compile
11 without warnings for the primary target compiler when all warnings are
21 There are two acceptable commenting styles: block, line.  Block comments
22 are used to document a largeish block of code, typically a function. Sometimes
23 block comments are useful with a function to document a loop or a particularly
24 tricky part of an algorithm. Line comments are typically a single sentence on a
27 NOTE: Comments are most useful to convey the purpose, parameters and results
33 that excessive line comments are a sort of "code smell" that may mean your
55 All indentation must be spaces, not tabs. Lines are indented in multiples of
63 Multiple word names are descriptive and most easily read if words are
75 Exceptions to these rules are made for compliance with the TCG
94 Single letter variable names should be avoided.  Exceptions are:
95 * "i", "j", and "k" are loop counters or temporary array indexes
96 * "m" and "n" are row and column indexes for multidimensional arrays
97 * "c" and "s" are temporary/parameter characters or strings
98 * "r", "g", "b", and "a" are red, green, blue, and alpha levels, but only when
99 * they are used together
100 * "x", "y", and "z" are coordinate values
102 Abbreviated words in variable names should be avoided.  Exceptions are:
113 to reflect the true condition even if they are created to detect false
145 file. Exceptions to this rule are generally limited to modules that will
149 Files names are formatted in the same way as described above with the
161 header of the same name, but should \#include files whose resources are used
162 within the source even if they are already included in that header. This
169 * System headers - These are headers provided by the core c libraries
171 * External dependencies - These are headers installed on the platform defining
173 * Standard TSS2 headers - These are headers that define the public TSS2 types
174 and interfaces. They are all located under $(srcdir)/include/* and will be
177 * Internal headers - These are headers defining the interfaces to code modules
178 that are internal to the project.
276 These formatting conditions are contrary to Kernighan and Ritchie's "one true brace style" [3].