On Thu, 16 Oct 2008, Jim Meyering wrote:
This one is perhaps a good reason to turn off or ignore that warning,
Thanks to Paul Eggert for finding an acceptable solution.
In general, I reiterate the principle I implied with my request that
#include_next warnings be suppressed some time ago: gnulib (and source
libraries in general) should not generate warnings. I should be able to use
whatever warning régime pleases me without having to worry about getting
warnings from 3rd party code.
I could have missed some warnings that will be very hard to avoid this way,
but I typically use fairly high warnings dosages when compiling my own code,
and so far I've not had many problems with gnulib. gnulib in particular,
since it's supposed to be portable, should not have too many problems
remaining pretty warning free. I see that in principle GCC support for
turning off warnings in 3rd-party code might be nice, although I'm a bit
dubious, as by leaving them on one's more likely to find odd bugs in gnulib.
(I'm not so interested in gnulib's ability to avoid triggering warnings in
other compilers; I've noticed in the past that some warning workarounds are
mutually exclusive depending on which compiler you want to please.)
--
http://rrt.sc3d.org/ | wisdom, n. knowing when to be foolish
