-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bruno Haible on 4/27/2008 5:27 PM: | Hi Jim, | |> The only non-POSIX behaviour is that it fetches the yesexpr and noexpr from |> a compiled PO file rather than from the system's nl_langinfo function. | | Here is a proposed compromise that enables the strict POSIX behaviour when | POSIXLY_CORRECT is set. This is a POSIX compliance fix for the programs | 'cp', 'mv', 'rm', 'find', 'xargs'.
That looks like a reasonable compromise to me. | | Tested with the 'yesno' module. (Why does the 'rpmatch' module not have a | unit test? Why does it not even have an include file that declares the | rpmatch function?) It has only been relatively recently that we started writing decent unit tests; rpmatch has been in gnulib relatively unchanged for quite some time. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgVvLAACgkQ84KuGfSFAYCCeACdG8B5+e9UrV7mdK9KgleXHfrI PEgAmgN/OQHHlDmIJF2cwAvp7E2mrc7s =EtOs -----END PGP SIGNATURE-----
