Home | History | Annotate | Download | only in coding_guidelines

Lines Matching full:separate

672 // Good: separate arguments with spaces, function name
771 // Bad: missing spaces all over (whitespace should be used to separate expressions)
1335 or as a separate <i>Blitter</i> class. Same applies to things such as reading texture from a file,
1382 some of the members into separate state-only classes whose sole responsibility is maintaining
1434 necessarily a bad thing as it requires separating any non-trivial computation into separate
1484 into separate functions is recommended. Unit testing those pure functions is then much easier.</p>
1488 reasons. One way to work around that while remaining as pure as possible is to use separate output-only