Lines Matching full:them
85 do suggest them.
90 to document them as much as possible. That way, your program will be
209 there is no legal requirement for them, so we don't use them.
212 avoid using them in ways which a reader might reasonably understand as
304 modes for each of them.
308 `--compatible' option to turn them off. However, if the extension has
325 is any precedent for them.
348 straightforwardly do without them, but to use the extensions if they
359 the GNU compiler, then no one can compile them without having them
486 we don't "obey" them.
505 "obey" them. In developing a GNU program, you should implement an
518 there are specific points on which we decided not to follow them, so as
612 give up on them.
619 are easy to examine with the debugger, so there is no point moving them
802 parse them. Note that the GNU version of `getopt' will normally permit
1013 please send <bug-standards@gnu.org> a list of them, with their
2106 operate on them.
2116 If your program creates complicated data structures, just make them
2179 definitions, and may also help certain tools recognize them. Thus,
2303 rewrite them. If you can't write comments in English, please find
2341 zero means continue them. */
2499 make a few abbreviations, explain what they mean, and then use them
2503 word commands can be useful within them. Stick to lower case; reserve
2565 MVS, and older Macintosh systems, supporting them is often a lot of
2618 with them. One way to print an `off_t' value portably is to print its
2736 can declare them in other files without any risk of type conflict.
2757 systems still don't support them. The string functions you can
2772 You may find it necessary to declare them *conditionally* on a few
2786 which don't support those names, define them as macros in terms of
2803 get them properly defined is to use Autoconf.
2814 in the program, and let gettext provide the way to translate them into
2970 different kinds of "ordinary files." Many of them support `mmap', but
3090 documentation; most of them are terse, badly structured, and give
3119 little additional text to go around them--but you must not do it. That
3138 manual is to use them as a source of information for writing good text.
3228 version they pertain to. Don't discard old items; leave them in the
3267 tell them what is in it. What they want from a change log is a clear
3289 advised that it is a good idea to include them, for the sake of
3328 Don't abbreviate function or variable names, and don't combine them.
3340 then don't put blank lines between them. Then you can omit the file
3457 expected for every GNU program to have a man page, but some of them do.
3572 trying to edit them by hand.
3587 the sources in one of these places, it should use them from there.
3625 them:
3659 is preferable to setting them in environment variables:
3796 build directory. So Makefile rules to update them should put the
3830 since a few systems don't support them.
3878 need to replace them with other programs.
3885 but we keep them because they are standard.) Use `CPPFLAGS' in any
3891 compilation of certain files, do not include them in `CFLAGS'. Users
3894 of `CFLAGS', by writing them explicitly in the compilation commands or
4136 types of files, if your program has them. Every GNU package should
4196 them as `@htmldir@', `@dvidir@',
4198 documentation should install them in `$(htmldir)/'LL,
4288 standard user-specified directories, it might be useful to group them
4301 believe all of them are. When any are missing, the descriptions here
4305 supports them.
4332 Do not strip executables when installing them. Devil-may-care
4352 The way to install Info files is to copy them into `$(infodir)'
4416 them. In simple cases, this target can use the `install' target in
4442 the distribution comes with them. There is no need to delete
4483 included in the distribution, we don't take care to make them easy
4523 them.
4590 # actually exist by making them if necessary.
4599 # actually exist by making them if necessary.
4647 categories, insert "category lines" among them. A category line
4655 _should not_ define them in the makefile).
4697 its own method of installing them--so it does not need to run the normal
4726 numbers, but it is very unlikely that you really need them.
4757 normally will never modify them. We commonly include non-source files
4792 regex, getopt, obstack, or termcap, include them in the distribution
4793 file. Leaving them out would make the distribution file a little
4805 people from using them, but we can and should refuse to advertise them
4836 anything to lead them to take an interest in it.
4961 regarding them.
5078 copies, to give them a chance to provide you with an updated
5196 unmodified, and list them all as Invariant Sections of your
