Lines Matching full:do

110 		we do y
114 while, do).  E.g.:
146 ie a ``while`` in a do-statement or an ``else`` in an if-statement, like
151 	do {
152 		body of do-loop
175 Do not unnecessarily use braces where a single statement will do.
224 	if, switch, case, for, do, while
233 Do not add spaces around (inside) parenthesized expressions.  This example is
271 Do not leave trailing whitespace at the ends of lines.  Some editors with
274 However, some such editors do not remove the whitespace if you end up not
288 and Pascal programmers, C programmers do not use cute names like
298 have descriptive names, as do global functions.  If you have a function
362        ``unsigned long``, then there's no reason to do
405 Functions should be short and sweet, and do just one thing.  They should
407 as we all know), and do one thing and do that well.
412 case-statement, where you have to do lots of small things for a lot of
420 it's performance-critical, and it will probably do a better job of it
446 Do not use the ``extern`` keyword with function prototypes as this makes
577 That's OK, we all do.  You've probably been told by your long-time Unix
579 you, and you've noticed that yes, it does do that, but the defaults it
585 values.  To do the latter, you can stick the following in your .emacs file:
639 But even if you fail in getting emacs to do sane formatting, not
677 	  logging of avc messages output).  Does not do system-call
740 Macros with multiple statements should be enclosed in a do - while block:
745 		do {					\
757 		do {					\
808 Kernel developers like to be seen as literate. Do mind the spelling
809 of kernel messages to make a good impression. Do not use crippled
810 words like ``dont``; use ``do not`` or ``don't`` instead.  Make the messages
813 Kernel messages do not have to be terminated with a period.
906 appears outweighs the potential value of the hint that tells gcc to do
936 recommended that they do.
960 Do not use bool if cache line layout or size of the value matters, as its size
993 There are also min() and max() macros that do strict type checking if you
1025 Do not include any of these in source files.  People have their own personal
1036 with CPU or platform functionality.  Don't hesitate to do so when necessary.
1037 However, don't use inline assembly gratuitously when C can do the job.  You can
1050 do so, though, and doing so unnecessarily can limit optimization.