>>>>> "MB" == Miles Bader <mi...@gnu.org> writes:
MB> [Or, perhaps, not "-Wall" perse, but maybe a new option which MB> is a little more conservative, "-Wstandard" or something...] Sure. Making a few more of the -W flags on by default may be OK, depending on the chosen list. It is the idea of turing all possible warning options on by default which is unreasonable. Defaulting to -Wall also fails as a user interface design. -Wall is a nice, short, sweet, easy to type optiong which one readily can add at any time. Forcing one to have to find all of the -Wno-... options to avoid unwanted annoyances, or to the -Wno-all and a set of -Ws which one does want is far more cumbersome. And what if new warning are added. Does anyone really want them *all* on by default as soon as the code lands? If there are some useful warning not already on by default which tend not to false-positive and provide useful, beneficial information when triggered, then it is reasonable to look into starting to default-enable them. Turning *all* of them on willy-nilly is not. -JimC -- James Cloos <cl...@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
