It is a while since we released Cppcheck-2.6. Do we want to release Cppcheck-2.7 sometime soon? Does it sound good to aim for early January? I don't have a strong opinion.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's a good idea to release the new version in early January from my side. On my Christmas wish list there are two MISRA-FPs to fixed before the release :-) misra-c2012-8.4 misra-c2012-10.4
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok if I might suggest something as well: this https://trac.cppcheck.net/ticket/10324 causes our developers to lose trust in cppcheck, because these unreadVariable messages increase the number of findings that (in most cases) need no fix. Even worse, we've seen people skip initializing variables in order to avoid this message, leading to actual errors.
Bottom line: if there's an unreadVariable or redundantAssignment finding, that's actually/also a redundantInitialization finding, then only a redundantInitialization should be output.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would suggest that we aim for a release on february 5th. It gives us some more time to fix false positives etc. Feel free to complain if you think it's too soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is a while since we released Cppcheck-2.6. Do we want to release Cppcheck-2.7 sometime soon? Does it sound good to aim for early January? I don't have a strong opinion.
If there's goodies in there, go for it.
It's a good idea to release the new version in early January from my side. On my Christmas wish list there are two MISRA-FPs to fixed before the release :-)
misra-c2012-8.4
misra-c2012-10.4
Then I suggest a feature freeze starts now, at least no major improvements.
Let's try to fix bugs. And we can discuss in early January if we are ready to release.
Thanks Daniel Marjamaki.. Looking forward to your Jan release that supports MISRA C..
I fear that cppcheck is far too unstable. this is not ok: http://cppcheck1.osuosl.org:8000/crash.html
one ticket: https://trac.cppcheck.net/ticket/10665
Most of those are assertion failures and not actual crashes, although there are still some new crashes that are not from asserts.
This causes a couple dozen FPs in our code base. It would be nice to get this fixed in 2.7.
Ok if I might suggest something as well: this https://trac.cppcheck.net/ticket/10324 causes our developers to lose trust in cppcheck, because these unreadVariable messages increase the number of findings that (in most cases) need no fix. Even worse, we've seen people skip initializing variables in order to avoid this message, leading to actual errors.
Bottom line: if there's an unreadVariable or redundantAssignment finding, that's actually/also a redundantInitialization finding, then only a redundantInitialization should be output.
Good work so far! 👍
The crash report is looking OK now.
I would suggest that we aim for a release on february 5th. It gives us some more time to fix false positives etc. Feel free to complain if you think it's too soon.