Lines Matching refs:be

5 …0. Code will not be wrapped to 80 characters. We all have 24+ inch high-res displays. Let's use th…
7  1. File names shall be camel case and descriptive. Keep them short too. Eg: spi.h is better than
9  2. All function names shall be camel-case, beginning with a lowercase letter.
12  4. All functions not visible in the global scope shall be declared static.
13  5. Functions taking no parameters shall be declated as (void) and not as ().
14  6. All type names shall be camel-case, beginning with a capital letter.
16  8. There should be *NO* globally-visible variables. All non-stack variables shall be declared
18 …9. All global variables in a given C file shall begin with "m" and then be in camel case. This is …
20 10. All variables shall be declared in the beginning of the block where they reside. This facilitat…
30 15. All structures shall be packed to avoid space waste, as the compiler is not allowed to pack the…
50     This will be enforced at compile time and will fail your build. This is intentional as the power
52 25. Do not cast floats to 64-bit values or back, this is slow. Use floatRt.h. This will be enforced
58 99. These guidelines will be kept updated as things come up/are decided.