Lines Matching full:them
76 do suggest them.
81 to document them as much as possible. That way, your program will be
195 we don't use them. There is no legal requirement for them.
198 avoid using them in ways which a reader might read as naming or labeling
281 modes for each of them.
285 `--compatible' option to turn them off. However, if the extension has
302 is any precedent for them.
325 straightforwardly do without them, but to use the extensions if they
336 the GNU compiler, then no one can compile them without having them
539 give up on them.
546 are easy to examine with the debugger, so there is no point moving them
714 parse them. Note that the GNU version of `getopt' will normally permit
845 please send <bug-standards@gnu.org> a list of them, with their
1936 on them.
1946 If your program creates complicated data structures, just make them
2003 definitions, and may also help certain tools recognize them. Thus, the
2121 rewrite them. If you can't write comments in English, please find
2159 zero means continue them. */
2317 make a few abbreviations, explain what they mean, and then use them
2321 word commands can be useful within them. Stick to lower case; reserve
2383 Macintosh, VMS, and MVS, supporting them is often a lot of work. When
2427 with them. One way to print an `off_t' value portably is to print its
2442 machines where there is a difference, all of them support Standard C
2522 can declare them in other files without any risk of type conflict.
2543 systems still don't support them. The string functions you can
2558 You may find it necessary to declare them *conditionally* on a few
2572 which don't support those names, define them as macros in terms of
2589 get them properly defined is to use Autoconf.
2600 in the program, and let gettext provide the way to translate them into
2686 different kinds of "ordinary files." Many of them support `mmap', but
2797 documentation; most of them are terse, badly structured, and give
2822 little additional text to go around them--but you must not do it. That
2841 manual is to use them as a source of information for writing good text.
2931 version they pertain to. Don't discard old items; leave them in the
2970 tell them what is in it. What they want from a change log is a clear
3026 Don't abbreviate function or variable names, and don't combine them.
3038 then don't put blank lines between them. Then you can omit the file
3134 expected for every GNU program to have a man page, but some of them do.
3232 trying to edit them by hand.
3247 the sources in one of these places, it should use them from there.
3270 distinguish them.
3336 configuration on which you will compile them, but the configure script
3340 cross-compiler you must specify them both explicitly.
3435 build directory. So Makefile rules to update them should put the
3469 since a few systems don't support them.
3517 need to replace them with other programs.
3524 but we keep them because they are standard.) Use `CPPFLAGS' in any
3530 compilation of certain files, do not include them in `CFLAGS'. Users
3533 of `CFLAGS', by writing them explicitly in the compilation commands or
3818 standard user-specified directories, it might be useful to group them
3853 Do not strip executables when installing them. Devil-may-care
3873 The way to install Info files is to copy them into `$(infodir)'
3915 them. In simple cases, this target can use the `install' target in
3940 with them.
3975 included in the distribution, we don't take care to make them easy
4062 # actually exist by making them if necessary.
4071 # actually exist by making them if necessary.
4119 categories, insert "category lines" among them. A category line
4127 _should not_ define them in the makefile).
4169 its own method of installing them--so it does not need to run the normal
4227 normally will never modify them. We commonly include non-source files
4269 regex, getopt, obstack, or termcap, include them in the distribution
4270 file. Leaving them out would make the distribution file a little
4282 people from using them, but we can and should avoid helping to
4283 advertise them to new potential customers. Proprietary software is a
4301 lead them to take an interest in it.
4388 philosophical, ethical or political position regarding them.
4481 copies, to give them a chance to provide you with an updated
4581 unmodified, and list them all as Invariant Sections of your
