-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Jim Meyering on 10/30/2007 7:18 AM: >> It's the xprintf.c code which calls vprintf(), bypassing printf(). Since >> this is a detail that the gnulib user should not know about, we should >> introduce a module 'xprintf-posix' that causes xprintf to have POSIX >> semantics for the formatted output. It will depend on xprintf and >> vprintf-posix. I'll do it later today if you don't beat me to it. > > That makes sense. > It will be less invasive, too. > Thanks. I'll let you do it :)
And we should probably do something similar by adding error-posix, verror-posix, and xvasprintf-posix. For example, m4 1.4.10 uses xvasprintf for its `format' builtin, and I had to manually pull in vasprintf-posix by looking at the implementation details of xvasprintf.c. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHJ3/l84KuGfSFAYARAti7AJ9F0Fhi7KbmyF3sKvkmQWfyRVVCNwCcCWUy 7B8gl/SdS8zTTbuFBsbHkE0= =L+AI -----END PGP SIGNATURE-----
