DJ Delorie <[EMAIL PROTECTED]> writes: | > . Next, if it would not be rejected on the "we don't want to have such | > functionality" basis, then the question becomes one of what should the | > interface look like? Some possibilities include: | > | > #pragma GCC command-line -Wprecision-mismatch | > | > unilaterally set -Wprecision-mismatch | | I was planning on proposing something like: | | #pragma GCC diagnostic [warning|error|ignore] -Wprecision-mismatch | | The diagnostic machinery already has support for some of this, I had | hoped to find time to make it fine-grained, allowing you to override | the KIND of each warning, and thus override -Werror on a | per-warning-type basis.
GCC's current architecture, heavily relying on global states, is not yet prepared to consistently support such feature -- even though the sole diagnostic machinery might be somewhat prepared for that. I think it would take more auditing of the -whole- compiler bundle than just the small diagnostic part of it to arrive to a decent state. That said, I'm very reluctant to that approach, for reasons mostly expressed by Robert Dewar. -- Gaby
