-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 3/9/2007 6:20 PM:
> This module adds a POSIX compliant printf() function. This is the last module
> in this series.
>
> Redefining 'printf' is less easy than redefining 'vprintf' etc., because
> gcc allows to use the symbo
This module adds a POSIX compliant printf() function. This is the last module
in this series.
Redefining 'printf' is less easy than redefining 'vprintf' etc., because
gcc allows to use the symbol 'printf' in __attribute__s of function
declarations. Working around this requires some tricks. You can
Here's a small fix for internationalization.
2007-03-09 Bruno Haible <[EMAIL PROTECTED]>
* lib/vasnprintf.c (VASNPRINTF): For the 'a' and 'A' directives, use
a locale dependent decimal point, rather than always '.'.
*** lib/vasnprintf.c5 Mar 2007 03:14:53 - 1.25
-
Eric Blake wrote:
And I don't know why Matthew's posts seem to be dropped from bug-gnulib, but
show up on m4-discuss:
Hmm, that's a good question. They seem to be getting through to list
subscribers (or at least gmane's subscription), as I can see them (I'm
using gmane's NNTP gateway). Howeve
Eric Blake wrote:
> Is this patch acceptable?
Yes. If somebody will be hurt by it (for example because the wait status
macros like WCOREDUMP give a different result for exit code 1 than for
exit code -1), it will be Matthew. Other platforms with EXIT_FAILURE = -1,
such as Sinclair QL, are not amon
Eric Blake <[EMAIL PROTECTED]> wrote:
> Is this patch acceptable? Most platforms already use 1 for EXIT_FAILURE. It
> fixes what are otherwise false negatives in the M4 testsuite. It also makes
> it
> easier to use GNU applications with xargs (since POSIX requires xargs to
> behave
> different
Is this patch acceptable? Most platforms already use 1 for EXIT_FAILURE. It
fixes what are otherwise false negatives in the M4 testsuite. It also makes it
easier to use GNU applications with xargs (since POSIX requires xargs to behave
differently when apps exit with 255 as compared with any o
