[Kde-imaging] [Digikam-devel] Coverty Reports traces...
Gilles Caulier
caulier.gilles at gmail.com
Tue Feb 5 10:06:35 UTC 2013
Note to all,
I checked other static code parser over digiKam 3.0.0-RC tarball,
especially in open source as ccpcheck,
Clang<http://en.wikipedia.org/wiki/Clang>,
Codan, etc... to see if i can found similar report than Coverity, and i can
said that none can be compared to this closed source parser.
http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis
Yes, using a closed source program to check open source code can be a
strange approach, but analisys results are really good.
Coverity has a Scan opensource program which is used now by all major
project that you know, as whole Linux kernel !
http://en.wikipedia.org/wiki/Coverity#Scan_.28Open_Source.29
http://scan.coverity.com/all-projects.html
so why not to use it too...
Note : I plan to buy a Coverity licence at work to parse all old code of
project managed in my office (where a lots of developers are left). I have
seen that Coverity is used in high level and critical process, as Nuclear
plan, Research center as CERN (to found Boson stuff), Bank, etc... It's
serious parser/analyser. And i can confirm that reports are sometimes very
instructive to found real bugs...
Gilles
2013/2/5 Gilles Caulier <caulier.gilles at gmail.com>
> Andrew,
>
> Yes, please. This will save time for me... (:=)))
>
> Thanks in advance
>
> Gilles
>
>
> 2013/2/5 Andrew Goodbody <ajg02 at elfringham.co.uk>
>
>> Hi Gilles,
>>
>> I have some time today. Would you like me to take a look at
>> BatchProcessImages?
>>
>> Andrew
>>
>>
>> On 03/02/13 17:33, Gilles Caulier wrote:
>>
>>> Thanks Benjamin,
>>>
>>> It still :
>>>
>>> - FlickrExport ==> (me)
>>> - RajceExport ==> (Lukas Krejci ?)
>>> - GalleryExport ==> (me)
>>> - VKontakteExport ==> (Alexander Potashev ?)
>>> - PrintImages ==> (Angelo Naselli ?)
>>> - ImgurExport ==> (Marius Orcsik)
>>> - PiwigoExport ==> (Frederic Coiffier ?)
>>> - DLNAExport ==> (Smit Mehta ?)
>>> - RemoveRedEyes ==> (Andi Clemens ?)
>>> - VideoSlideshow ==> (me)
>>> - BatchProcessImages ==> (me if time permits)
>>>
>>> Gilles
>>>
>>>
>>> 2013/2/3 Benjamin Girault <benjamin.girault at gmail.com
>>> <mailto:benjamin.girault@**gmail.com <benjamin.girault at gmail.com>>>
>>>
>>>
>>> Hi,
>>>
>>> 2013/1/31 Benjamin Girault <benjamin.girault at gmail.com
>>> <mailto:benjamin.girault@**gmail.com <benjamin.girault at gmail.com>>>:
>>>
>>> > I'll try to fix "bugs" of ExpoBlending since I am
>>> > already familiar with that part of the code.
>>>
>>> Done.
>>>
>>> Cheers,
>>>
>>> --
>>> Benjamin.
>>> ______________________________**_________________
>>> Kde-imaging mailing list
>>> Kde-imaging at kde.org <mailto:Kde-imaging at kde.org>
>>> https://mail.kde.org/mailman/**listinfo/kde-imaging<https://mail.kde.org/mailman/listinfo/kde-imaging>
>>>
>>>
>>>
>>>
>>>
>>> ______________________________**_________________
>>> Digikam-devel mailing list
>>> Digikam-devel at kde.org
>>> https://mail.kde.org/mailman/**listinfo/digikam-devel<https://mail.kde.org/mailman/listinfo/digikam-devel>
>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-imaging/attachments/20130205/893ea4ea/attachment.html>
More information about the Kde-imaging
mailing list