This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: The meaning of -Wall
On Sat, 3 May 2003, Bruce Korb wrote:
> cart; and when you try you may not be able to. So, it goes back to
> designing an interface that is easy to manipulate. Command line
There's always writing a wrapper script called "gcc" and placing it
earlier in the PATH - hardly good style, but it can accomplish option
rewriting and configuration if thousands of Makefiles can't be modified.
(You might need another script called "cc" as well, and if an absolute
path is used then need to replace the installed gcc.) Then there's
modifying the installed specs file - even worse style, has to be redone
for each new version and specs interfaces are obscure (not suitable for
average users) and subject to change, but also allows a lot of option
rewriting.
With all the ways available of configuring and rewriting options, I think
the value of a configuration file (in any usual sense of one intended for
users to modify; people can always shoot themselves in their feet with
modifications to the specs file or other parts of the installation if they
don't really know what they're doing) for FSF GCC is negative; GCC-based
IDEs however might well have such a configuration file of their own.
What would be useful in FSF GCC is pragmas for fine-grained warning
control within source files.
--
Joseph S. Myers
jsm28@cam.ac.uk