Lines Matching refs:program
129 to document them as much as possible. That way, your program will be
153 If you have a vague recollection of the internals of a Unix program,
160 memory use; if you go for speed instead, your program will be very
163 recently than the Unix program. Eliminate use of temporary files. Do
172 dynamic allocation instead. Make sure your program handles NULs and
174 for extensibility and write part of the program in that language.
176 Or turn some parts of the program into independently usable libraries.
185 If the program you are working on is copyrighted by the Free Software
187 the program, we need legal papers to use it---just as we asked you to
189 contribution to a program must sign some sort of legal papers in order
190 for us to have clear title to the program; the main author alone is not
198 This applies both before you release the program and afterward. If
223 reached the stage of actually maintaining a program for GNU (whether
250 @cindex program design
253 account when designing your program.
282 program. For example, if you write your program in C++, people will
283 have to install the GNU C++ compiler in order to compile your program.
287 program if it is written in C.
308 for a language that is higher level than C. Often much of the program
345 defined with a null value). Please make your program recognize this
363 extensions in implementing your program is a difficult question.
365 On the one hand, using the extensions can make a cleaner program.
366 On the other hand, people will not be able to build the program
368 program to work on fewer kinds of machines.
401 so if you know how to do that, feel free. If a program you are
466 program we prefer using @code{if (... )} over conditional compilation,
566 you wish to run your program on Unix, and wish to avoid lossage in this
573 If @code{malloc} fails in a noninteractive program, make that a fatal
574 error. In an interactive program (one that reads commands from the
583 When static storage is to be written in during program execution, use
600 to make a program portable. If you use @code{signal}, then on GNU/Linux
615 Do not use a count of errors as the exit status for a program.
617 bits (0 through 255). A single run of the program might have 256
619 will see 0 as the status, and it will appear that the program succeeded.
658 together, so that no reasonable program could use one without the
698 @var{program}:@var{source-file-name}:@var{lineno}: @var{message}
705 @var{program}: @var{message}
714 @var{program}:@var{source-file-name}:@var{lineno}:@var{column}: @var{message}
717 In an interactive program (one that is reading commands from a
718 terminal), it is better not to include the program name in an error
719 message. The place to indicate which program is running is in the
720 prompt or with the screen layout. (When the same program runs with
725 it follows a program name and/or file name. Also, it should not end
735 @cindex program name and its behavior
736 @cindex behavior, dependent on program's name
744 @cindex output device and program's behavior
745 Likewise, please don't make the behavior of the program depend on the
761 program with a preferred alternate version that does not depend on the
762 output device type. For example, we provide a @code{dir} program much
771 When you write a program that provides a graphical user interface,
778 separate program which invokes the command-line program.) This is
795 command-line options of a program. The easiest way to do this is to use
808 consistent from program to program. For example, users should be able
809 to expect the ``verbose'' option of any GNU program which has one, to be
812 for your program (@pxref{Option Table}).
828 This option should direct the program to print information about its name,
831 is seen, and the program should not perform its normal function.
833 @cindex canonical name of a program
834 @cindex program's canonical name
835 The first line is meant to be easy for a program to parse; the version
837 the canonical name for this program, in this format:
844 The program's name should be a constant string; @emph{don't} compute it
846 name for the program, not its file name. There are other ways to find
849 If the program is a subsidiary part of a larger package, mention the
858 program's version number, you can mention the package version number
862 are distributed separately from the package which contains this program,
867 Please do not mention all of the libraries that the program uses ``just
876 Next should follow a brief statement that the program is free software,
878 the program is covered by the GNU GPL, say so here. Also mention that
882 program, as a way of giving credit.
897 You should adapt this to your program, of course, filling in the proper
898 year, copyright holder, name of program, and the references to
903 versions' changes. You don't have to mention the name of the program in
928 program, on standard output, then exit successfully. Other options and
929 arguments should be ignored once this is seen, and the program should
948 incomplete, but we aim to list all the options that a new program might
1744 program accepting @samp{--quiet} should accept @samp{--silent} as a
1858 @strong{Note:} every program accepting
2065 If a program typically uses just a few meg of memory, don't bother making any
2073 If a program works by lines and could be applied to arbitrary
2078 If your program creates complicated data structures, just make them in
2086 are read-only file systems. Thus, if the program manages log files,
2092 configuration information; it is reasonable for a program to modify
2095 is reasonable for the program to store other files in the same
2166 program in version 1.2 and newer. It corresponds to the options
2178 of styles within one program tends to look ugly. If you are
2179 contributing changes to an existing program, please follow the style of
2180 that program.
2199 We find it easier to read a program when it has spaces before the
2257 Please use formfeed characters (control-L) to divide the program into
2266 Every program should start with a comment saying briefly what it is for.
2269 Please write the comments in a GNU program in English, because English
2391 all its uses. This makes the program even cleaner.
2497 Don't make the program ugly to placate @code{lint}. Please don't insert any
2505 The names of global variables and functions in a program serve as
2508 function. In a GNU program, names should be English, like other
2546 names. You can use the program @code{doschk} to test for this.
2560 versions. For a GNU program, this kind of portability is desirable, but
2578 use Autoconf. It's unlikely that your program needs to know more
2597 you define the same function names in some other way in your program.
2599 to make the program more portable to other systems.)
2742 Because @code{xmalloc} and @code{xrealloc} are defined in your program,
2792 program. (Nowadays, it is better to choose @code{strchr} and
2823 messages in a program into various languages. You should use this
2824 library in every program. Use English for the messages as they appear
2825 in the program, and let gettext provide the way to translate them into
2839 Once a program uses gettext, please make a point of writing calls to
2939 A GNU program should ideally come with full free documentation, adequate
2977 program; it may be irrelevant and confusing for a user.
2989 For example, each program in the GNU system probably ought to be
2990 documented in one manual; but this does not mean each program should
3001 The manual which discusses a program should certainly document all of
3002 the program's command-line options and all of its commands. It should
3006 program does.
3030 the program. One combined Index should do for a short manual, but
3051 computer program. Please use ``invalid'' for this, and reserve the term
3088 frequently than or independent of the program, also state a version
3091 Each program documented in the manual should have a node named
3092 @samp{@var{program} Invocation} or @samp{Invoking @var{program}}. This
3093 node (together with its subnodes, if any) should describe the program's
3096 containing a template for all the options and arguments that the program
3108 each program described in the manual.
3125 be a good idea to include the program's license in a large manual; in a
3127 the program's license, it is probably better not to include it.
3170 Keep a change log to describe all the changes made to program source
3175 inconsistencies between different parts of a program, by giving you a
3299 documentation says with the way the program actually works.
3363 expected for every GNU program to have a man page, but some of them do.
3364 It's your choice whether to include a man page in your program.
3367 requires continual effort each time the program is changed. The time
3370 For a simple program which changes little, updating the man page may be
3374 For a large program that changes a great deal, updating a man page may
3383 When a program changes only a little, you may feel that the
3394 program you are documenting.
3399 a certain program works, and these facts are necessarily the same for
3425 @cindex program configuration
3430 kind of machine and system you want to compile the program for.
3439 build the program without configuring it first.
3445 won't be able to build the program without configuring it first.
3460 program was last configured. This file should be a shell script which,
3466 the program in a separate directory, so that the actual source directory
3482 type of system to build the program for. This argument should look like
3517 @samp{--enable} is for questions of whether to build part of the program
3555 program may be different.
3558 system as both the host and the target, thus producing a program which
3585 your program is set up to do this, your @code{configure} script can simply
3603 Building and installing the program should never modify any of the files
3605 part of the program in any way must be classified into @dfn{source
3635 installing the program should @strong{never} be included in the
3648 characters long. Likewise, no file created by building the program
3673 Likewise, if your program uses small GNU software packages like regex,
3683 A GNU program should not recommend use of any non-free program. We
3690 When a non-free program or system is well known, you can mention it in
3694 how to use it together with some widely used non-free program.
3697 who already use the non-free program to use your program with
3699 proprietary program, and don't imply that the proprietary program
3700 enhances your program, or that its existence is in any way a good
3702 program will get the advice they need about how to use your free
3703 program, while people who don't already use the proprietary program
3706 If a non-free program or system is obscure in your program's domain,
3707 your program should not mention or support it at all, since doing so
3708 would tend to popularize the non-free program more than it popularizes
3709 your program. (You cannot hope to find many additional users among