mirror of
https://git.savannah.gnu.org/git/gnulib.git
synced 2025-08-17 12:41:05 +03:00
61c96af09d
The POSIX folks admitted that codifying the behavior of GNU getopt on a leading '+' in optstring is worthwhile, for writing programs such as env(1) even when POSIXLY_CORRECT is not defined. http://austingroupbugs.net/view.php?id=191 However, the ruling is an enhancement request for the next version of POSIX, and is not binding on platforms that comply with POSIX 2008, so it should only be enforced for getopt-gnu. * tests/test-getopt.h (test_getopt): Strengthen tests of leading '+' handling, when requesting extensions. * tests/test-getopt_long.h (test_getopt_long): Strengthen test of 'W;' handling. * m4/getopt.m4 (gl_GETOPT_CHECK_HEADERS): Detect glibc 2.11 bug. * doc/posix-functions/getopt.texi (getopt): Document this. * doc/glibc-functions/getopt_long.texi (getopt_long): Likewise. * doc/glibc-functions/getopt_long_only.texi (getopt_long_only): Likewise.
71 lines
2.6 KiB
Plaintext
71 lines
2.6 KiB
Plaintext
@node getopt
|
|
@section @code{getopt}
|
|
@findex getopt
|
|
|
|
POSIX specification: @url{http://www.opengroup.org/onlinepubs/9699919799/functions/getopt.html}
|
|
|
|
Gnulib module: getopt-posix or getopt-gnu
|
|
|
|
The module @code{getopt-gnu} has support for ``long options'' and for
|
|
``options that take optional arguments''. Compared to the API defined by POSIX,
|
|
it adds a header file @code{<getopt.h>} and a function @code{getopt_long}.
|
|
|
|
Portability problems fixed by either Gnulib module @code{getopt-posix} or @code{getopt-gnu}:
|
|
@itemize
|
|
@item
|
|
The @code{getopt} function keeps some internal state that cannot be explicitly
|
|
reset on some platforms:
|
|
mingw.
|
|
@item
|
|
The value of @code{optind} after a missing required argument is wrong
|
|
on some platforms:
|
|
MacOS 10.5.
|
|
@end itemize
|
|
|
|
Portability problems fixed by Gnulib module @code{getopt-gnu}:
|
|
@itemize
|
|
@item
|
|
The function @code{getopt} does not support the @samp{+} flag in the options
|
|
string on some platforms:
|
|
MacOS X 10.5, AIX 5.2, HP-UX 11, IRIX 6.5, OSF/1 5.1, Solaris 10.
|
|
@item
|
|
The function @code{getopt} does not obey the combination of @samp{+}
|
|
and @samp{:} flags in the options string on some platforms:
|
|
glibc 2.11.
|
|
@item
|
|
The function @code{getopt} does not obey the @samp{-} flag in the options
|
|
string when @env{POSIXLY_CORRECT} is set on some platforms:
|
|
Cygwin 1.7.0.
|
|
@item
|
|
The function @code{getopt} does not support options with optional arguments
|
|
on some platforms:
|
|
MacOS X 10.5, OpenBSD 4.0, AIX 5.2, HP-UX 11, IRIX 6.5, OSF/1 5.1,
|
|
Solaris 10, Cygwin 1.5.x.
|
|
@item
|
|
The function @code{getopt_long} is missing on some platforms:
|
|
AIX 5.1, HP-UX 11, IRIX 6.5, OSF/1 5.1, Solaris 9, Interix 3.5.
|
|
@item
|
|
The function @code{getopt_long_only} is missing on some platforms:
|
|
MacOS X 10.3, FreeBSD 5.2.1, NetBSD 3.0, AIX 5.1, HP-UX 11, IRIX 6.5,
|
|
OSF/1 5.1, Solaris 9, mingw, Interix 3.5.
|
|
@end itemize
|
|
|
|
Portability problems not fixed by Gnulib:
|
|
@itemize
|
|
@item
|
|
The default behavior of the glibc implementation of @code{getopt} allows
|
|
mixing option and non-option arguments on the command line in any order.
|
|
Other implementations, such as the one in Cygwin, enforce strict POSIX
|
|
compliance: they require that the option arguments precede the non-option
|
|
arguments. This is something to watch out in your program's
|
|
testsuite.
|
|
@item
|
|
The glibc implementation allows a complete reset of the environment,
|
|
including re-checking for @env{POSIXLY_CORRECT}, by setting
|
|
@code{optind} to 0. Several BSD implementations provide @code{optreset},
|
|
causing a reset by setting it non-zero, although it does not
|
|
necessarily re-read @env{POSIXLY_CORRECT}. Solaris @code{getopt} does
|
|
not support either reset method, but does not maintain state that
|
|
needs the extra level of reset.
|
|
@end itemize
|