Lines Matching +full:use +full:- +full:external +full:- +full:names

18 yourself disabling `-Werror` you're probably doing something wrong.
28 from functions and objects in a system. Excessive use of comments within a
42  * unlike the Post-It style content of next-line and line comments.
56 4 spaces. Each line of code and documentation will end with a non-whitespace
61 Names should clearly convey the purpose of whatever is being named. While the
63 Multiple word names are descriptive and most easily read if words are
66 Variable and function names must be lowercase. Words in each name must be
68 declared with \#define) must be in all-caps, again with words separated by
72 with individual words in object names as upper case characters.
76 specifications. All function names, parameters, and other data types must
94 Single letter variable names should be avoided.  Exceptions are:
102 Abbreviated words in variable names should be avoided.  Exceptions are:
110 Function names should follow the naming conventions of variables and clearly
130 A function that is exported for use in multiple source files should be
137 The use of the static keyword when defining functions is a useful way to scope
146 expose a separate set symbols to external consumers. In this case the internal
147 version of the header should be suffixed with '-priv'.
149 Files names are formatted in the same way as described above with the
150 exception of hyphens "-" separating words.
154 which they reside. Their names shall be all caps, with words separated by
169 * System headers - These are headers provided by the core c libraries
171 * External dependencies - These are headers installed on the platform defining
172 interfaces to external libraries.
173 * Standard TSS2 headers - These are headers that define the public TSS2 types
177 * Internal headers - These are headers defining the interfaces to code modules
183 header: `example-module.h`
196 #include "internal-module.h"
205 implementation: `example-module.c`
218 #include "example-module.h"
219 #include "internal-module.h"
227 Types shall be selected for their use case. Variables should only be of a
228 signed type if something should ever be negative. A common, incorrect use, is
229 to declare loop counters as int instead of unsigned, or to use an int to hold
233 Always use space characters, 4 spaces per level of indentation.
279 1. GNOME C Coding Style : https://developer.gnome.org/programming-guidelines/stable/c-coding-style.…
280 …ding Standards, 2001, http://www.alma.nrao.edu/development/computing/docs/joint/0009/2001-02-28.pdf