cppcheck warnings... Mostly fixed, but not few one...
caulier.gilles at gmail.com
Thu May 17 20:59:11 BST 2018
Look also the noExplicitConstructor entries :
Currently, with Krazy static analyzer, i disable the warnings, and all
re-appear with cppcheck.
This is a tedious problem. Try to force a missing explicit constructor, as :
>From Face Management code, and you will see a lots of errors.
Typically, the right constructor choice is delegate to the compiler, and
the state at run time can be undefined. This is especially the case for
contructor with one argument or more than one but with 2nd, 3rd, etc...
using default values.
I already fixed some simple case, but it's the hell to apply fix
everywhere, and i'm sure that side effect are introduced without explicit
More details here :
2018-05-17 19:19 GMT+02:00 Gilles Caulier <caulier.gilles at gmail.com>:
> Hi all,
> I very well advanced with cppcheck static analyzer reports review, and i
> fixed around 300 entries since 2 weeks...
> But, as usual, the mostly difficult task is always at end, and the last
> reports sound like... special...
> Look this one :
> If we have really an error here, digiKam will crash very quickly when an
> image is open with DImg container. A false positive ?
> And what's about these 4 entries about equality operator :
> And definitively, i lost with these one :
> Where these virtual calls appears in source code ?
> Any tips, viewpoints, and guidance ?
> Gilles Caulier
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Digikam-devel