Fixed some minor cppcheck issues that we have with stricter settings #77
Conversation
This file contains hidden or 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
jesper-raemaekers
force-pushed
the
cppcheck-additional-rules
branch
from
5c85f87 to
c2f6a37
Compare
jesper-raemaekers
force-pushed
the
cppcheck-additional-rules
branch
from
b1b0171 to
ff46032
Compare
Contributor
|
Do you want to make my cppcheck config stricter too? |
pylessard
reviewed
Jul 13, 2025
Contributor
Author
I have now added just one additional parameter to the cppcheck config. If you agree it is probably nicer to add them in smaller PRs over time instead of one big one. |
Contributor
|
Sure as you wish. I wouldn't mind to make the code stricter as once. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
First small change mostly to see if jenkins runs on my PR. On our project we have stricter rules, this is one of them.