Paul Eggert wrote: > The goal here is software reliability not pacifying compilers
But when "gcc -Wall" reports 10 warnings to me, and I don't notice that one of them is an actual bug because I mentally discard all of them "oh these new warnings must all be false positives by gcc", there is something wrong in the way I worked. This happened to me today, with a full gnulib testdir. Hence my wish to silence the gcc warnings in gnulib, on recent glibc systems with recent gcc versions. > or clang, or whatever. I'm not talking about clang here. Clang produces tons of warnings, too much to be useful for my average use. Bruno
