---- Reported by email@example.com 2010-04-13 01:50:38 +0000 ----
This is from http://bugzilla.moblin.org/show_bug.cgi?id=3476
At Intel we have access to the static code analysis tool Klocwork. I found
Klocwork to be very useful. It nicely complements run-time error checking with
There are some concerns that using a closed source tool in an open source
project isn't fair to the community because they don't have access to it. I
agree to some extend: it's not fair to complain to someone about warnings that
he couldn't have found without access to the tool.
Some people reject closed source tools based on principles.
But I think improving the code quality by developing patches with the help of
such a tool is fair game. Synthesis would very much appreciate it if we did
Klocwork works best if integrated into the development process, in other words,
is used regularly. It does produce false positives which have to be identified
once, but only once when reusing the same Klocwork setup.
Perhaps this is something to be integrated into the nightly testing which I
intend to set up on an Intel-internal server.
--- Bug imported by firstname.lastname@example.org 2012-07-29 20:36 UTC ---
This bug was previously known as _bug_ 682 at https://bugs.meego.com/show_bug.cgi?id=682
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/110.