Lines Matching refs:it

14 files by typing 'indent myfile.c myfile.h' and it will magically apply all the
41 This is everybody's favorite flame topic so let's get it out of the way right
56 	\t * Note that it has multiple lines
81 	While it extends the line a bit longer, the spaced version is more
83 	excluding the spacing makes it more obvious that we are dealing with a
84 	single term (even if it is a compound term) such as:
96 If an opening bracket starts a function, it should be on the
97 next line with no spacing before it. However, if a bracket follows an opening
98 control block, it should be on the same line with a single space (not a tab)
99 between it and the opening control block statement. Examples:
131 it easier for reader to notice that 2nd and following lines are still
144 and the left paren that starts it's parameter list (whether it is being
226 name, but it's not a policy of busybox project to enforce such a minor detail).
236 because it looks like whitespace; using lower-case is easy on the eyes.
283    does not do the actual conversion, rather, it generates a script called
300 the 'convertme.pl' script you should run it on _all_ files like so:
327 Although enum may look ugly to some people, it is better for code size.
328 With "const int" compiler may fail to optimize it out and will reserve
329 a real storage in rodata for it! (Hopefully, newer gcc will get better
330 at it...).  With "define", you have slight risk of polluting namespace
334 whatsoever, making it much more error prone.
362 Code cluttered with ifdefs is difficult to read and maintain. Don't do it.
438 The use of the "equals" (==) operator in the latter example makes it much more
440 "not" (!) operator makes it look like you are testing for an error. In a more
457 gets         string it gets             fgets
461 [vf]scanf    its arguments              just avoid it
511 it's needed), but can be a problem in some low resource machines that have
537 formatting, options, etc.), model it after the equivalent GNU program.
540 programs after their GNU counterparts and it will make life easier on (nearly)
553 use the output, it should really be fixed.
559 If a const variable is used only in a single source file, put it in the source
561 one function, do not make it global to the file. Instead, declare it inside
570 immediate file, turn it into a general-purpose function with no ties to any
571 applet and put it in the utility.c file instead.
577 Please use brackets on all if and else statements, even if it is only one
605 laugh, it happens to us all.) Remember folks, this is C, not Python.
659 		/* if the search string is in this line, print it,
675 basically it boils down to two things: at the top of the .c file, have this