DJ Delorie wrote:
For example, if you have two warnings in one statement, you can't
control one but not the other if they use the same -W option. A minor
point, but if we used line numbers we'd be really close to "this
should work" that people would claim it's a bug when it doesn't.
Seems rather marginal to worry about this. Surely this is letting best
be the
enemy of good. And as for it being a bug, that's just a matter of clear
documentation.
Plus, we'd need to keep track of a linked list of flag state
structures.
Sounds doable ...
Some folks made convincing arguments that it wouldn't always work the
way the user wanted, too. We don't always have a line number, for
example. Which warning state takes effect? When we have a "first
used here" type diagnostic, which warning state is used?
Well the warning is going to be issued at some source location in
any case, so the answer is that the suppression or control has to
apply to that location.
But I'm willing to implement something if people think it's the best
thing to do.
