Implemented suppressing warnings using error message text #1302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is to add support for suppressing a warning using the text of its warning message, plus wildcards. This is useful for suppressing warnings like knownConditionTrueFalse (which has no symbol) when they are emitted for code within a macro. There is no other way of doing a specific suppression for this.
|
Do you face a situation similar to https://trac.cppcheck.net/ticket/3537? |
|
We should probably skip the error when a literal is used. Thats what I did for PR #1294. |
I'd prefer the other solution, though... |
|
So PR #1304 should fix the FP with knownConditionTrueFalse when the condition is a literal. |
|
I close this PR. Fixing the FP is prefered. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I encountered a situation where I wanted to suppress a warning that was being emitted by an assert macro:
"knownConditionTrueFalse: Condition '!true' is always false"
Because this warning has no symbol and comes from many locations, there was no other way to suppress it than by introducing this functionality.