-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Mikhail Teterin on 9/21/2006 9:24 PM: > FreeBSD's, surely, is fine: > > [EMAIL PROTECTED]:/tmp (67) uname -a > FreeBSD aldan.algebra.com 6.1-STABLE FreeBSD 6.1-STABLE #0: Fri Jul 28 > 11:06:03 EDT 2006 [EMAIL PROTECTED]:/meow/obj/var/src/sys/SILVER amd64 > [EMAIL PROTECTED]:/tmp (68) env POSIXLY_CORRECT=1 ./foo > OpenBSD getopt > [EMAIL PROTECTED]:/tmp (69) ./foo > GNU getopt
No, it is FreeBSD that is broken. If you use getopt_long to implement the POSIX requirements of "pr -s _", the GNU version complies whether or not POSIXLY_CORRECT is set (POSIX requires it to interpret -s with no argument, using TAB as default; and treat _ as a filename), while the FreeBSD version would actually violate POSIX when you have specifically requested POSIX compliance (by treating _ as the character argument of -s and using stdin). > > Do I have you converted yet? Nope. All you have managed to do is convince me that GNU m4 and gnulib should continue rejecting the current FreeBSD getopt_long implementation as broken. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----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 iD8DBQFFE15e84KuGfSFAYARAlhRAJ4+nXJvj54YQHRbD4sUvyogXf6ZLACeP6EO 5eL7DE6t5VPQdpUtrw/q+4M= =C1Zm -----END PGP SIGNATURE-----
