Lines Matching full:programs
46 * Program Behavior:: Program behavior for all programs
48 * Documentation:: Documenting programs.
63 guide to writing portable, robust and reliable programs. It focuses on
64 programs written in C, but many of the rules and principles are useful
123 * Reading Non-Free Code:: Referring to proprietary programs.
130 2.1 Referring to Proprietary Programs
134 work on GNU! (Or to any other proprietary programs.)
153 Or go for generality. For example, Unix programs often have static
207 We have more detailed advice for maintainers of programs; if you have
228 naming or labeling our own programs or activities. For example, since
295 Many programs are designed to be extensible: they include an
304 GUI functionality within Guile. We don't reject programs written in
314 With occasional exceptions, utility programs and libraries for GNU
325 a significant chance of breaking any real programs or scripts, then it
329 Many GNU programs suppress extensions that conflict with POSIX if the
334 When a feature is used only by users (not by programs or command
367 An exception to this rule are the large, established programs (such
369 extensions in such programs would make many users unhappy, so we don't
372 Another exception is for programs that are used as part of
386 features in new programs. There is one exception: do not ever use the
390 features in programs. It is ok to use its features if they are present.
393 programs, so if you know how to do that, feel free. If a program you
492 4 Program Behavior for All Programs
503 * Semantics:: Writing robust programs.
527 users--it means that their programs or scripts will work more portably.
531 shell script writers and users would be unhappy if our programs were
564 4.2 Writing Robust Programs
576 those characters. Whenever possible, try to make programs work
724 Error messages from other noninteractive programs should look like
751 Error messages from interactive programs, and other messages such as
781 Compatibility requires certain programs to depend on the type of
806 running programs, such as within GNOME. (GNOME used to use CORBA for
844 All programs should support two standard options: `--version' and
845 `--help'. CGI programs should accept these as command-line options,
1017 help using GNU programs. The format should be like this:
1031 Here is a table of long options used by GNU programs. It is surely
1086 For server programs, run in the background.
1119 Used in various programs to make output shorter.
1131 Used in various programs to specify the directory to use.
1224 Specify the directory to use, in various programs. In `ls', it
1341 For server programs, run in the foreground; in other words, don't
1450 In some programs, specify the name of the file to read as the
1657 Used in various programs to inhibit warnings.
1711 In various programs, specify the output file name.
1804 Used in many programs to inhibit the usual output. Every program
1916 Used in many programs to inhibit the usual output. Every program
2081 Print more information about progress. Many programs support this.
2181 However, for programs such as `cat' or `tail', that can usefully
2198 Programs should be prepared to operate when `/usr' and `/etc' are
2287 causes no problems for users if two different programs have different
2470 meaningful. This not only makes programs easier to understand, it also
2598 Some GNU programs were designed to limit themselves to file names of
2601 existing GNU programs that have it, but there is no need to do this in
2602 new GNU programs. `doschk' also reports file names longer than 14
2631 because most of the programs that need such knowledge have already been
2662 to move your code into other GNU programs.
2685 counterexample: 64-bit programs on Microsoft Windows. We will leave it
2686 to those who want to port GNU programs to that environment to figure
2754 reduce portability, and in most programs they are easy to avoid. In the
2803 Most GNU programs use those functions just once, in functions
2856 for new programs, since those are the standard names.) Declare
2999 In the C locale, GNU programs should stick to plain ASCII for quotation
3043 some do not. It is important to make programs handle all these kinds
3049 6 Documenting Programs
3119 manual for "comparison of files" which covers both of those programs,
3120 as well as `cmp'. By documenting these programs together, we can make
3218 The title page of the manual should state the version of the programs or
3239 If one manual describes several programs, it should have such a node
3478 C programs often contain compile-time `#if' conditionals. Many changes
3760 configuration options in GNU software. We do not want GNU programs to
3783 The target type normally defaults to the host type. Programs for
3788 Some programs have ways of configuring themselves automatically. If
3799 programs. Using Automake will help you write a Makefile that follows
3827 Different `make' programs
3839 you need to run programs that are a part of your package during the
3911 Stick to the generally supported options for these programs. For
3919 compilers and related programs, but should do so via `make' variables
3921 programs we mean:
3926 Use the following `make' variables to run those programs:
3957 In particular, you should run most utility programs via variables.
3964 need to replace them with other programs.
4120 Executable programs are installed in one of the following
4124 The directory for installing executable programs that users can
4130 The directory for installing executable programs that can be run
4137 The directory for installing executable programs to be run by other
4138 programs rather than by users. This directory should normally be
4151 * Some files are normally modified by programs; others are never
4201 programs
4207 which the programs modify while they run. This should normally be
4212 The directory for installing data files which the programs modify
4228 programs with the C `#include' preprocessor directive. This
4399 All GNU programs should have the following targets in their Makefiles:
4409 that executable programs have debugging symbols. Users who don't
4661 programs in which they are useful.
4729 Most programs don't need any pre-installation commands, but we have
4772 programs except for these:
4787 Programs to build binary packages work by extracting the
4823 files by programs under the control of the Makefile.
4892 can't stop some people from writing proprietary programs, or stop other
4934 non-free platform in order to run. For instance, many Java programs
4936 program is to promote the other programs it needs. This is why we are
4937 careful about listing Java programs in the Free Software Directory: we
4943 recommend, promote or legitimize programs that depend on non-free
4946 Some free programs strongly encourage the use of non-free software.
4954 Thus, you should not recommend programs that strongly encourage the
5075 composed of pixels) generic paint programs or (for drawings) some
5509 * CGI programs, standard options for: Command-Line Interfaces.
5640 * proprietary programs: Reading Non-Free Code.
