achieving my real goal:
Helping less experienced Perl developers avoid pitfalls that would lead to hard to understand issues
Suggest you perform some detailed code reviews with your inexperienced Perl developers and write items found during the review on a wiki page, especially noting issues that crop up often. That way, you grow your list of common pitfalls over time based on real world issues in your environment. You may be able to evolve this into a code review checklist.
Detailed reviews take time, so I normally run beginner's Perl code through Perl::Critic before the code review.
-
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.
|
