Lines Matching full:do

132 		we do y
136 while, do).  E.g.:
168 ie a ``while`` in a do-statement or an ``else`` in an if-statement, like
173 	do {
174 		body of do-loop
197 Do not unnecessarily use braces where a single statement will do.
246 	if, switch, case, for, do, while
255 Do not add spaces around (inside) parenthesized expressions.  This example is
293 Do not leave trailing whitespace at the ends of lines.  Some editors with
296 However, some such editors do not remove the whitespace if you end up not
310 Unlike Modula-2 and Pascal programmers, C programmers do not use cute
320 have descriptive names, as do global functions.  If you have a function
403        ``unsigned long``, then there's no reason to do
446 Functions should be short and sweet, and do just one thing.  They should
448 as we all know), and do one thing and do that well.
453 case-statement, where you have to do lots of small things for a lot of
461 it's performance-critical, and it will probably do a better job of it
490 Do not use the ``extern`` keyword with function declarations as this makes
641 That's OK, we all do.  You've probably been told by your long-time Unix
643 you, and you've noticed that yes, it does do that, but the defaults it
649 values.  To do the latter, you can stick the following in your .emacs file:
703 But even if you fail in getting emacs to do sane formatting, not
745 	  logging of avc messages output).  Does not do system-call
808 Macros with multiple statements should be enclosed in a do - while block:
813 		do {					\
839 	#define macrofun(foo) do { (void) (foo); } while (0)
848 		do {					\
899 Kernel developers like to be seen as literate. Do mind the spelling
900 of kernel messages to make a good impression. Do not use incorrect
901 contractions like ``dont``; use ``do not`` or ``don't`` instead. Make the
904 Kernel messages do not have to be terminated with a period.
998 appears outweighs the potential value of the hint that tells gcc to do
1028 recommended that they do.
1052 Do not use bool if cache line layout or size of the value matters, as its size
1085 There are also min() and max() macros that do strict type checking if you
1117 Do not include any of these in source files.  People have their own personal
1128 with CPU or platform functionality.  Don't hesitate to do so when necessary.
1129 However, don't use inline assembly gratuitously when C can do the job.  You can
1142 do so, though, and doing so unnecessarily can limit optimization.
1205 22) Do not crash the kernel
1221 Do not add new code that uses any of the BUG() variants, such as BUG(),
1226 "I'm too lazy to do error handling" is not an excuse for using BUG(). Major
1239 Do not WARN lightly
1249 Do not worry about panic_on_warn users
1254 there is a "Do not WARN lightly" writeup, above. However, the existence of