Paul Eggert <egg...@cs.ucla.edu> writes: > On 11/30/11 02:10, Simon Josefsson wrote: >> the philosophy behind the manywarnings module is >> to enable all possible kind of warnings that you can get from gcc > > Hmm, OK, but in that case, shouldn't it be called "allwarnings" > rather than "manywarnings"? I got the impression from its name > that it doesn't enable every warning in sight....
The intention with the module is that packages get "many" (not all) warnings enabled, however the gl_MANYWARN_ALL_GCC function (which was modified here, and is just one part of the module) should list "all" warnings. Renaming the module "allwarnings" sounds a bit confusing as well, since the purpose is not to enable all warnings... but I don't care strongly about the name. /Simon
