First, I want to thank everyone who responded to my request for comments on Perl::Critic. Based on your invaluable feedback, we've made a number of signficant enhancements:
- Several Monks suggested that Perl::Critic should focus on only the most offensive or risky coding practices, or else it might seem too alarming and annoying. So we've assigned severity levels to all the "Policy" modules. By default, Perl::Critic only complains about high-severity issues. Of course, you may not agree with our severity designations, so you can override them to suit your own tastes. And by increasing the severity threshold over time, you can gradually whip your legacy code into shape.
- We've also added a dozen new "Policy" modules. Most of these come from Conway's "Perl Best Practices." But we've also taken a few ideas from B::Lint. So I think Perl::Critic is starting to demonstrate its capacity to support a range of alternate stylistic views.
- This node about a use stricter pragma inspired me to create the criticism module to accompany Perl::Critic. At first I thought it was mostly a joke, but I'm beginning to think that criticism has real merit.
So once again, I welcome any ideas, comments, or complaints. The lastest version of Perl::Critic is on CPAN now. Thanks, and 'Gung Hay Fat Choy!'
-Jeff
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|