Subject: Re: [boost] Maintainers: Adding Coverity Scan to your library
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2017-10-12 22:07:29
On 12 October 2017 at 16:02, Alexander Zaitsev via Boost
> 12.10.2017 16:17, Niall Douglas via Boost Ð¿Ð¸ÑÐµÑ:
>> On 12/10/2017 14:02, James E. King, III via Boost wrote:
>>> Even if you do not have travis integration in your library, running a
>>> manual scan will help you improve the quality of your library, so I
>>> recommend everyone at least do that much.
>> I don't have positive experiences with Coverity. Nor with their tech
>> If you're going to run a lint tool, the most recent clang-tidy is hard
>> to beat, even compared to very expensive commercial lint tools. Plus, it
>> can rewrite your code to fix the lint problem for you. Much faster and
> You can use free cppcheck or PVS-Studio (free for header files).
Any reference to support that?
AFAIK, there is more steps involved and no mention of special licensing
for headers or header-only libraries https://www.viva64.com/en/b/0457/
> I have good experience with these tools.
-- Mateusz Loskot, http://mateusz.loskot.net
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk