On Oct 25, 2006, at 3:23 PM, jerry gay wrote:
one overall test for perlcritic is fine with me. there's nothing
stopping us from parsing perlcritic output if we want a different
format, however i'd rather not go that far.
additionally, i'd like to see less verbose output from perlcritic. the
thousands of lines of diag output from a single test file is
...distracting. i'm sure it's configurable, but i haven't taken the
time to look into it. do you have any quick suggestions, or should i
dive into the docs?
~jerry
Jerry:
* open t/codingstd/perlcritic.t
* search for "-format"
* look at the below URL for the allowed sprintf-like codes
http://search.cpan.org/~thaljef/Perl-Critic-0.2/lib/Perl/Critic/
Violation.pm#OVERLOADS
The current format is:
-format => '[%p] %m at %l,%c',
which yields
"[TestingAndDebugging::RequireUseStrict] Code before
strictures are enabled at 235,1"
If you want to see fewer errors, add
-top => 5
after the -format to only show the first 5 violations per .pm file.
Chris
--
Chris Dolan, Software Developer, Clotho Advanced Media Inc.
608-294-7900, fax 294-7025, 1435 E Main St, Madison WI 53703
vCard: http://www.chrisdolan.net/ChrisDolan.vcf
Clotho Advanced Media, Inc. - Creators of MediaLandscape Software
(http://www.media-landscape.com/) and partners in the revolutionary
Croquet project (http://www.opencroquet.org/)
