7.15.1 getopt feature limitations
This list of limitations is relative to the full list of AutoOpts
supported features, See AutoOpts Features.
- You cannot automatically take advantage of environment variable options or
automated parsing of configuration files (
rc
or ini
files).
Consequently, the resulting code does not support --load-opts or
--save-opts options automatically.
- You cannot use set membership, enumerated, range checked or stacked
argument type options. In fact, you cannot use anything that depends
upon the
libopts
library. You are constrained to options that
take string
arguments, though you may handle the option
argument with a callback procedure.
- Special disablement and/or enablement prefixes are not recognized.
- Option coordination with external libraries will not work.
- Every option must be
settable
because the emitted code
depends upon the SET_OPT_XXX
macros having been defined.
Specify this as a global (program) attribute.
- You must specify a main procedure attribute (see Generating main procedures).
The getopt.tpl template depends upon being able to compile the
traditional .c file into a program and get it to emit the usage text.
- For the same reason, the traditional option parsing table code must be
emitted before the getopt.tpl template gets expanded.
- The usage text is, therefore, statically defined.