Lines Matching refs:We

7 We're not perfect. Please be polite where you notice these discrepancies and we'll try to be polite…
14 We've tried to keep our standard simple because we also believe that we can only expect someone to …
20 We're C developers and embedded software developers.
39 We believe that if you're working with a simple compiler and target, you shouldn't need to configur…
45 We name files, functions, variables, and so much more.
57 We want to read our code.
59 We try to avoid double negatives.
60 We try to avoid cryptic abbreviations (sticking to ones we feel are common).
64 We like descriptive names for things, especially functions and variables.
68 We're okay with a bit more typing if it means our code is easier to understand.
76 We find i, j, and k are better loop counters than loopCounterVar or whatnot.
77 We only break this rule when we see that more description could improve understanding of an algorit…
81 We like consistency, but we're not really obsessed with it.
82 We try to name our configuration macros in a consistent fashion... you'll notice a repeated use of …
97 We don't really want to add to the style battles out there.
103 We've decided on our own style preferences.
105 It will only hurt a little. We promise.
111 We have no more reason than that.
112 We break that rule when we have lines that wrap (macros or function arguments or whatnot).
153 We apologize.
154 We think they are ugly too.
160 We'll keep it really brief!
166 We have no more reason than that.
167 We break that rule when we have lines that wrap.
182 We use markdown and we like PDF files because they can be made to look nice while still being porta…