Warning about unused suppressions

[Samuel Poláček]

I was wondering how to manage suppressions with different versions of cppcheck.
Maybe a suppressions file with cppcheck version in its name?

It seems to me that it makes sense to warn about, for example, an unused inline suppression. The suppression might be there because it is a false positive that may get resolved with a new version of cppcheck, which would basically render the suppression not irrelevant, but, I would argue, incorrect.

I know that I have not described the problem in full, but this should be enough to plant an idea.

What is your opinion?

[Daniel Marjamäki]

I was wondering how to manage suppressions with different versions of cppcheck.
Maybe a suppressions file with cppcheck version in its name?

I would envision it's best if all developers use the same Cppcheck version. Provided through a container or VM or in the repository, etc..

It seems to me that it makes sense to warn about, for example, an unused inline suppression. The suppression might be there because it is a false positive that may get resolved with a new version of cppcheck, which would basically render the suppression not irrelevant, but, I would argue, incorrect.

That is exactly what Cppcheck does as far as I know.