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, AIX 7.1.
@end itemize
Portability problems fixed by Gnulib module @code{getopt-gnu}:
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 glibc implementation allows a complete reset of the environment,
including re-checking for @env{POSIXLY_CORRECT}, by setting
-@code{optind} to 0. Other implementations provide @code{optreset},
+@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}.
+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