Lines Matching full:good
431 both cases, and we have been using similar techniques with good success
712 It is a good idea to follow the POSIX guidelines for the command-line
730 It is usually a good idea for file names given as ordinary arguments
2216 facilitates optimization by good compilers. You can also move the
2366 Beyond that, it is good to support the other free operating systems
2388 It is a good idea to define the "feature test macro" `_GNU_SOURCE'
2724 makes it possible to produce a good quality formatted book, using TeX,
2732 documentation by conversion this way, as long as it gives good results.
2736 this structure is not necessarily good for explaining how to use the
2745 write good documentation is learning to notice when you are structuring
2771 should give a good introduction to a beginner reading through from the
2773 Bison manual is a good example of this--please take a look at it to see
2786 Bison manual provides a good example of how to do this.
2792 The Texinfo manual includes advice on preparing good index entries, see
2840 The only good way to use documentation strings in writing a good
2841 manual is to use them as a source of information for writing good text.
2890 can be a good idea to include the program's license in a large manual;
3033 not a good idea, since searching for `jump-to-register' or
3382 it is a good idea to set the suffix list explicitly using only the
3468 It is a good idea to avoid creating symbolic links in makefiles,
4211 is also good to explain the purpose of each of the first-level
4297 program, or that its existence is in any way a good thing. The goal
