> Regardless of that sort of issue, I think on previous occasions when the > topic of MISRA (or other coding standard) checking came up, there has > been a general opinion from the gcc developers that the compiler itself > is not the best place for this sort of checking - they recommend an > external tool, and don't want the main code base cluttered with such > specific warnings for the dozens of coding standards in common use.
Note that there's also a legal issue here: when one has to obtain a license from MISRA.
