Re: The meaning of -Wall

[Bruce Korb <bkorb at veritas dot com>]

"Joseph S. Myers" wrote:

> With all the ways available of configuring and rewriting options,

[albeit ugly ways ;-]

> I think the value of a configuration file ... for FSF GCC is negative

OK.  We'll always disagree on that.  If the available ways for doing
something are ugly, then it's worth making life easier.

> 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.

Still and all, if you're going to add such pragmas, it should be
made a trivial mapping:

  #pragma gcc_option  Wall
  #pragma gcc_option  no-warn-unused-static

and if I choose to use it in some other way:

  #pragma gcc_option  I /path/to/proj/headers

let it fail only because it is too difficult to be handled,
and not because the code cannot understand the request
or because the code believes I shouldn't want to make
such a request.