Re: getopt_long and POSIXLY_CORRECT

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Mikhail Teterin on 9/22/2006 11:10 AM:
> п'ятниця 22 вересень 2006 13:04, Andrey Chernov написав:
>> On Fri, Sep 22, 2006 at 01:22:42AM -0400, Mikhail Teterin wrote:
>>> The GNULIB folks are calling BSD's getopt_long implementation "broken",
>>> because -- unlike theirs -- it respects the POSIXLY_CORRECT environment
>>> variable, when working with an opstring containing "::" (signifying an
>>> optional value for a particular flag).
>> Fixed in getopt_long.c v1.13
> 
> Thanks, Andrey. Please, make sure, the change gets into upcoming FreeBSD-6.2 
> too.

Is there a link to an online CVS repository with this change?  If the
FreeBSD getopt_long v1.13 file behaves like GNU's getopt in all aspects
(including the reason that sparked this exchange, where in GNU
getopt_long, optional arguments using :: have no change in behavior
whether or not POSIXLY_CORRECT is specified, since POSIX does not require
disabling this extension), then gnulib needs to be patched to detect if
the BSD getopt_long has the fix.

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFFCc484KuGfSFAYARAsISAJ9nYyXf+Pm1Lkte5mOG1VGxo+w3TwCgrx3y
4ALNfQHHu6jGWsq0V2kY6sg=
=/mmF
-----END PGP SIGNATURE-----