Re: more cleanups

2009-11-19 Thread Jim Meyering
Eric Blake wrote: > I noticed these while trying to build m4 and diffutils: > > From: Eric Blake > Date: Thu, 19 Nov 2009 08:51:13 -0700 > Subject: [PATCH 1/2] text-xvasprintf: silence compiler warnings s/text/test/ > * tests/test-xvasprintf.c (test_xvasprintf, test_xasprintf): Mask > empty str

Re: [PATCH] xfreopen: new module, from coreutils

2009-11-19 Thread Jim Meyering
Eric Blake wrote: > Jim Meyering meyering.net> writes: >> I am about to use this from diff, so... >> BTW, changed license from LGPL in coreutils to GPL here, since >> it doesn't make sense to use error-generating code from a library. > > xfreopen still doesn't deal with the problem of whether a st

more cleanups

2009-11-19 Thread Eric Blake
I noticed these while trying to build m4 and diffutils: From: Eric Blake Date: Thu, 19 Nov 2009 08:51:13 -0700 Subject: [PATCH 1/2] text-xvasprintf: silence compiler warnings * tests/test-xvasprintf.c (test_xvasprintf, test_xasprintf): Mask empty string from gcc. Signed-off-by: Eric Blake ---

Re: [PATCH] xfreopen: new module, from coreutils

2009-11-19 Thread Eric Blake
Jim Meyering meyering.net> writes: > > I am about to use this from diff, so... > BTW, changed license from LGPL in coreutils to GPL here, since > it doesn't make sense to use error-generating code from a library. xfreopen still doesn't deal with the problem of whether a stream should be reopen

[PATCH] xfreopen: new module, from coreutils

2009-11-19 Thread Jim Meyering
I am about to use this from diff, so... BTW, changed license from LGPL in coreutils to GPL here, since it doesn't make sense to use error-generating code from a library. >From ba4000b09804294e46373afb2003744612096a20 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Thu, 19 Nov 2009 15:55:58 +01

Re: improving manywarnings

2009-11-19 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 11/7/2009 10:06 AM: > I'm considering using manywarnings in m4, and noticed that newer gcc > supports even more warnings. I noticed several warnings supported by gcc > 4.3.4 --help=warnings that were not listed already; see