3rdparty is used by the not quite used parrot backend, as well as the
path src/vm/parrot.
So I guess it does make sense to scan the MoarVM repository, but not NQP.
Am 21.10.2015 um 01:47 schrieb Jeffrey Ryan Thalhammer:
> 37 of them come from a path matching /3rdparty/
>
> The rest come from a
37 of them come from a path matching /3rdparty/
The rest come from a path matching /src/
You can tune all of this via scan.coverity.com
Hope that helps.
-Jeff
> Coverity can check the C source code for NQP, but AFAIK doesn't work
> on code written in NQP.
>
That is correct. Only C, C++, C#, Objective-C, Java, & JavaScript.
PHP and Python are scheduled for next year. Perhaps Perl6 will be too some
day.
But the C source for NQP shows 119 potential
I am curious how many of those are parrot vs. moarvm (and if moarvm,
how many are the 3rd party dependencies)
On Mon, Oct 19, 2015 at 4:56 PM, Jeffrey Ryan Thalhammer
wrote:
>
>> Coverity can check the C source code for NQP, but AFAIK doesn't work
>> on code written in NQP.
>
Hello everyone-
I'm a longtime Perl5 developer and the creator of Perl::Critic. More
recently, I started working for Coverity, which makes commercial static
analysis tools.
Coverity offers a free analysis service through scan.coverity.com. This
service is used by thousands of open source
Coverity can check the C source code for NQP, but AFAIK doesn't work
on code written in NQP.
On 10/19/15, Tobias Leich wrote:
> "Coverity Scan Static Analysis - Find and fix defects in your Java,
> C/C++, C# or JavaScript open source project for free"
>
> How does that work for
"Coverity Scan Static Analysis - Find and fix defects in your Java,
C/C++, C# or JavaScript open source project for free"
How does that work for code written in NQP?
Cheers, Tobias
Am 17.10.2015 um 00:38 schrieb Jeffrey Ryan Thalhammer:
> Hello everyone-
>
> I'm a longtime Perl5 developer and