I used Perl::Critic 0.12 to clean some legacy
code and I was impressed. Now I see that the latest version
has many enhancements, and such a task should be much
I like the interface, although the policy names are a
little scary. If you could find a way of making them
shorter (or even identifiable by some acronym, for instance
ppwb as a shortcut to ProhibitParensWithBuiltins) perhaps
they could become a habit for command line enthusiasts.
As for your plan to enhancements, I see very favourably
your idea of covering most of Conway's book, but I don't
think I would use a feature that changes my code
automatically based on some rule. Sure it looks
interesting, but I produce just enough bugs manually, that
I don't need the ones introduced in my code
Kudos for this great job!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||