| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following global definitions are used to define attributes of the entire program. These generally alter the configuration or global behavior of the AutoOpts option parser. The first two are required of every program. The rest have been alphabetized. Except as noted, there may be only one copy of each of these definitions:
string->c_name! (see section 3.5.48 `string->c-name!' - map non-name chars to underscore).
ERRSKIP_OPTERR and ERRSTOP_OPTERR from the
generated interface file.
[), then there is no requirement on the presence or
absence of command line arguments following the options. Lastly, if it
is supplied and does not start with an open bracket, then option
processing must not consume all of the command line arguments.
PROGRAM_OPTNAME or PROGRAM, where PROGRAM is the
upper cased C-name of the program and OPTNAME is the
upper cased C-name of a specific option.
#include directives required by
flag_code text and shared with other program text.
Do not specify your configuration header (`config.h') in this
attribute or the include attribute, however. Instead, use
config-header, below.
.
or `/usr/local/share/progname') or an environment variable (like
`$HOME/rc/' or `$PREFIX/share/progname') or the directory
where the executable was found (`$$[/...]') to use to try to find
the rcfile. Use as many as you like. The presence of this attribute
activates the --save-opts and --load-opts options.
See section 7.7.1 RC or INI file presets.
flag_code program text.
long-opts. If
none of your options specify an option value (flag character) and you do
not specify long-opts, then command line arguments are processed
in "named option mode". This means that:
- and -- are completely optional.
argument program attribute is disallowed.
homerc attribute.
default: .<prog-name>rc
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |