Suggested feature : check only changed files

[Rob van den Bergh]

Before commit, I would like to (manually) re-check the changed files.
Without using a commit hook like svn provides, because I do not want to force fixes.
unfortunately I am dealing with a legacy project which (still) has a lot of cppcheck errors, so checking the whole tree will not be clear.
CppCheck has no option, to (for example) check only the non-readonly files in my code tree...
Kind regards,
Rob

[Daniel Marjamäki]

I am skeptic about adding such features to Cppcheck CLI. We try to keep that simple.

I believe in the "use multiple tools" philosophy. It is best if each tool only focus on producing as good warnings as possible. And all extra features are put in some wrapper so they can be reused for all tools.

Perhaps you could use a Makefile or a script to achieve what you want. If you do write something useful feel free to send it to us so we can publish it.

[Daniel Marjamäki]

In the Cppcheck GUI on the other hand.. I think such feature is appropriate. We already have a feature to only recheck changed files. Have you looked at this? Does it work badly for you?

[Rob van den Bergh]

Thnx for your replies,
I guess you mean the "recheck files" option from the menu / 2-rotating-arrows-icon.
It might re-process only the changed files, but the outputwindow still shows the output for ALL files right ? So I have no way to find only my checkedout files quickly.
Also, even if I would be able to find them, I would need to do a scan before my changes, leave it open (or save), and rescan afterwards. This would not be practical.

[Daniel Marjamäki]

Before commit, I would like to (manually) re-check the changed files.
...
CppCheck has no option, to (for example) check only the non-readonly files in my code tree...

If you write some script that extract the files you want to check.. using svn diff , filesystem search, etc.. then you can feed that output into cppcheck.

If you upload such script I will be happy to put it in the repo and mention it in the wiki/manual.

Also, even if I would be able to find them, I would need to do a scan before my changes, leave it open (or save), and rescan afterwards. This would not be practical.

I see your point. I agree that is not good.