Lines Matching full:put
881 for, put each on a separate line.
2167 It is important to put the open-brace that starts the body of a C
2306 Please put a comment on each function saying what the function does,
2319 Please put two spaces after the end of a sentence in your comments,
2390 else should go in a header file. Don't put `extern' declarations inside
2425 statement, always put braces around the `if'-`else'. Thus, never write
2741 *conditionalized* declarations of `malloc' and `realloc'--or put
2787 the other pair. For example, here is what to put at the beginning
3159 Alternatively, put a menu item in some menu whose item name fits one
3233 a file named `ONEWS' and put a note at the end referring the user to
3281 you're probably right. Please do explain it--but please put the
3340 then don't put blank lines between them. Then you can omit the file
3350 When you install someone else's changes, put the contributor's name
3479 updating. If so, put a prominent note near the beginning of the man
3796 build directory. So Makefile rules to update them should put the
3800 Makefile should not put it in the source directory, because building a
3908 Put `CFLAGS' last in the compilation command, after other variables
4079 to put these various kinds of files in:
4129 the package's operation; put such configuration information in
4171 To tell whether `foo.h' came from the Foo package, put a magic
4280 # Where to put the executable for the command `gcc'.
4282 # Where to put the directories used by the compiler.
4284 # Where to put the Info files.
5058 legibly, you should put the first ones listed (as many as fit
5303 the License in the document and put the following copyright and license
