david ingamells

Just found another: BOOST_PP_STRINGIZE https://www.boost.org/doc/libs/1_77_0/libs/preprocessor/doc/ref/stringize.html

Hi, Some time ago I reported a couple of missing defines in the config lib boost.cfg and I think they got added in version 2.8 - for which thanks! I have now discovered some more: define name="BOOST_TTI_HAS_TYPE(x)" value="" define name="BOOST_TTI_MEMBER_TYPE(x)" value="" define name="BOOST_TTI_HAS_STATIC_MEMBER_FUNCTION(x)" value="" Today I was pleased to see that there is also a wxwidgets.cfg config lib and had need to use it. I have discovered that there is a missing define there too: there is...

I cannot find any check for "Floating point expressions shall not be compared using either the == or != operators." - is there one? My company's standards justify this rule with: "Comparing floating point expressions for equality or inequality is a famous source of well-documented software system failures."

A request: Would it be possible to extend the output of --errorlist to list all the possible severities for each error id? That would make my work much easier. As it is now, apart from scouring through the source code of cppcheck, I don't see how I can know which severities are possible for each error id, or which error texts (e..g "might be" vs "is") can be produced.

Regarding how I used: --xml Write results in xml format to error stream (stderr). Regarding the severity, it is a surprise to me that an error Id can get 2 different severities, contrary to what the --errorlist says/implies. I have just implemented a filter that uses the--errorlist output's severities to determine how to treat each error id. Oh well, back to the drawing board.

With CPPCheck version 2.6: In the output of the --errorlist option, objectIndex is reported with severity "error" but when actually generated during a check run it is generated with severity "warning". I think the latter is more appropriate. cppcheck --errorlist | grep objectInd <error id="objectIndex" severity="error" msg="The address of local variable &apos;&apos; is accessed at non-zero index." verbose="The address of local variable &apos;&apos; is accessed at non-zero index." cwe="758"/> when...

In the output of the --errorlist option, objectIndex is reported with severity "error" but when actually generated during a check run it is generated with severity "warning". I think the latter is more appropriate. cppcheck --errorlist | grep objectInd <error id="objectIndex" severity="error" msg="The address of local variable &apos;&apos; is accessed at non-zero index." verbose="The address of local variable &apos;&apos; is accessed at non-zero index." cwe="758"/> when in the results of a code check:...

Hi, While using CPPCheck v 2.6 I have discovered that the error type constParameter that is generated during a run: <error cwe="398" file0="..." id="constParameter" msg="Parameter '_a' can be declared with const" severity="style" verbose="Parameter '_a' can be declared with const"> <location column="77" file="..." info="Parameter '_a' can be declared with const" line="94"/> </error> Is not listed in cppcheck's errorlist, i.e. $> cppcheck --errorlist | grep constParam $> I use the errorlist to categorise...