[Daca-general] Perl::Critic - standardising on an output format would be useful

[Alexey Shrub]

28.01.2011, 10:39, "Raphael Geissert" <geissert at debian.org>:
> Hi,
> On Friday 14 January 2011 11:43:16 Alexey Shrub wrote:
>>  For standardising output format you can use Test::Perl::Critic that print
>>  in standard TAP format - http://testanything.org Test::Harness can run
>>  many such tests and make report (use prove util or perl -MTest::Harness -e
>>  'runtests(@ARGV)' t/*.t), there is TAP parser on CPAN if need something
>>  else/ You can see example of such test in git repository
>>  https://github.com/worldmind/perl-test-code-quality-template/blob/master/xt
>>  /50-critic.t In this repsitory I try to collect test for perl code quality
>
> Thanks for your email. I've been playing with Perl::Critic and
> Test::Perl::Critic but I think I'm going to go with a custom output format.
>
> The problem I have with the TAP approach is that it doesn't really help me
> with the format of Perl::Critic's output. I would still have to parse the
> comments extracted via TAP::Parser.
>
> AFAICS running perlcritic(1) with a custom profile and a custom format (%f:%l:
> %c:%p:%s:%m\n) should be enough for DACA.
>
> Now, what still needs to be decided is what policies should be enabled, or if
> they should all be enabled. I think I'm more inclined to enabling them all (at
> least the 'core' ones) and filtering the results later.

If you want I can help you write script for perl code analysis

-- 
Alexey Shrub