Christophe Rhodes <csr21@...> writes:
> If you are worried about style-warning being too coarse a class to
> muffle, then thoughts on a sensible hierarchy of style-warning
> conditions that can be documented and exported from an extension
> package are appreciated.
I'm sorry, but I don't have any suggestions. In almost every case, it
would be better to code around this particular style warning, so I
couldn't justify putting it in any particular place in such a hierarchy.