Lines Matching full:we

5 For the most part, we try to follow these standards to unify our contributors' code into a cohesive…
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 …
19 Before we get into details on syntax, let's take a moment to talk about our vision for these tools.
20 We're C developers and embedded software developers.
25 Our philosophy is "support every compiler we can".
26 Most often, this means that we aim for writing C code that is standards compliant (often C89... tha…
31 A lot of Unity is configurable and we have worked hard to make it not TOO ugly in the process.
35 It's just what we do, because we like everything to Just Work™.
38 By that, we mean that we do our best to have EVERY configuration option have a logical default.
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.
46 While we're not always going to find the best name for something, we actually put a bit of effort i…
48 When naming things, we follow this hierarchy, the first being the most important to us (but we do a…
57 We want to read our code.
58 This means we like names and flow that are more naturally read.
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.
70 There are two exceptions to this rule that we also stick to as religiously as possible:
72 …hile we realize hungarian notation (and similar systems for encoding type information into variabl…
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 …
87 Where ever it doesn't violate the above principles, we try to apply memorable names.
88 … using something that is simply descriptive, but often we strive for descriptive AND unique... we …
89 Take a look through the file names in Ceedling and you'll get a good idea of what we are talking ab…
97 We don't really want to add to the style battles out there.
103 We've decided on our own style preferences.
104 If you'd like to contribute to these projects (and we hope that you do), then we ask if you do your…
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).
113 When that happens, we like to indent further to line things up in nice tidy columns.
141         //Like so. Even if only one line, we use braces.
147 Do you know what we hate?
149 BUT, we're using them anyway.
150 As we mentioned, our goal is to support every compiler we can, especially embedded compilers.
152 So that is what we're using.
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.
168 When that happens, we like to indent further to line things up in nice tidy columns.
182 We use markdown and we like PDF files because they can be made to look nice while still being porta…