Lines Matching refs:use

17 The source code must use the **UTF-8** character encoding. Comments and
18 documentation may use non-ASCII characters when required (e.g. Greek letters
31 Exceptions are made when referring directly to something that does not use
72 Use **tabs** for indentation. The use of spaces for indentation is forbidden
124 acceptable to use additional blank lines for clarity, if required.
175 For example, use the following style:
226 Local variables and function parameters use the same format as function names:
267 size of eight columns it would be necessary to use one tab character and two
322    * In this style, the first and last lines use asterisks that run the full
331   /* Single line comments can use this format */
359 All header files that are included by a source file must use the following,
417 codebase. Correct use of the two styles improves readability by suggesting the
422 including them, use the ``"..."`` variant.
425 is including them, use the ``<...>`` variant.
478 Some TF definitions use both a struct/enum name **and** a typedef name. This
481 function shall use the same names and type qualifiers".