Fix #14367: Support polyspace inline suppressions for misra c:20xx rules #8105
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
Should this be behind a flag? Always parsing for something very niche (and premium only?) seems undesired. |
I think that would be good. |
ludviggunne
force-pushed
the
14367
branch
2 times, most recently
from
565b38a to
d27f25b
Compare
Since it is specific to certain MISRA rules it should only be active if those rules are active. |
ludviggunne
force-pushed
the
14367
branch
2 times, most recently
from
73a5159 to
da0456b
Compare
|
| class CPPCHECKLIB Parser { | ||
| public: | ||
| Parser() = delete; | ||
| explicit Parser(const Settings &settings) : mSettings(settings) {} |
There was a problem hiding this comment.
Maybe the constructor could look at the settings and check if any misra rules are enabled. If no misra rules are enabled it would make sense if collect and parse will not do anything.
I agree it's niche use case. Especially for open source projects. imho.. if If misra checkers are not enabled then it's redundant to handle the polyspace comments. |
3 participants
No description provided.