Lines Matching refs:function

33  - function declarations (if necessary)
34  - function implementations
96 If an opening bracket starts a function, it should be on the
143 Put a space between C keywords and left parens, but not between function names
216 level (because they do not "belong" to block scope, only to whole function).
225 (Putting label at position 1 prevents diff -p from confusing label for function
235 acceptable). Using underscores makes variable and function names more readable
397 the "no-op" case (the empty function) when the feature is turned off.
399 Note also the use of the word 'maybe' in the function name to indicate
441 perfect world, we would have a streq() function in the string library, but
452 function     overflows                  preferred
475 	static char buffer[BUFSIZ]; /* happily used by any function in this file,
495 declared on the stack in the *_main() function and made available globally by
561 one function, do not make it global to the file. Instead, declare it inside
562 the function body. Bottom line: Make a conscious effort to limit declarations
567 function which must be declared extern.
569 If you write a function that performs a task that could be useful outside the
570 immediate file, turn it into a general-purpose function with no ties to any
611 Do not use old-style function declarations that declare variable types between