Thanks for your reply, but I didn't asked question you're replying to. I've asked how to speedup perlcritic, not is it make sense to use it.

My coding style is very good, and you can easily examine it yourself by checking my modules on CPAN or my open source software on my website.

So, I don't need perlcritic to improve my coding style. You probably know perl syntax good enough, but don't you find automated syntax check with perl -c on saving file very useful? We're all use it not because we don't know perl's syntax, but because it help us fix typos and mistakes early and easy. Same apply to use warnings and use strict. And same to perlcritic. They all help us have more safe and consistent coding style and warn about subtle issues at low cost and as early as possible.

But perlcritic work in such a way, what if it wasn't used on regular basis all of time since you begin writing code, there is high chance first time you run perlcritic you got dozens, or, even more likely, hundreds of warnings. EVEN if your coding style is really very good. Some of these warnings probably should be disabled at all, some ignored with ## no critic, some just not really important but better to change code in way perlcritic wants to make code style more consistent, and, finally, few warn about very important subtle issues. And chances are when you notice these hundreds of warnings first time, you decide to move one and ignore them all, because task of handling them all looks too scary. THIS IS WHY I want to run perlcritic each time when saving file - to handle it's warnings one by one, instead of dozens at once.

In reply to Re^2: perlcritic speedup by powerman
in thread perlcritic speedup by powerman

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.