comment on

Jenda,

Please don't hold back, tell us what you really think! :) OK, enough with giving you are hard time...

What I have found for Perl::Critic is that it is a good developer testing module. It seems you have some strong opinions about numerous rules for Perl::Critic and that is OK. However, Perl::Critic addresses two major concerns that I consider more important than the actual rules

Personal preference: It is easy enough to disable the rules you don't like.
Consistency: If there are two programmers working together, you would like them to be able to have some sort of consistency in the work between them.

Also since Perl::Critic is a developer testing module rather than a required distribution module, there is no reason that it should be an issue when writing your code.

It is a tool that should make you happier and help, not be an opinion that is forced on you.

In reply to Re^2: RFC: Perl-Critic policy: ProhibitInlineSystemArgs by Herkum
in thread RFC: Perl-Critic policy: ProhibitInlineSystemArgs by davidrw

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.


Do you know where your variables are?
	PerlMonks