But how are we going to know if what they did is the best practice or the best way to do that. Note that we dont have a senior level or an experience developer to check their code.
You could automate the process using Perl::Critic, which can be customized to highlight what you deem important.

Another effective method for checking code robustness is to run the code on the various platforms/OS's and versions of Perl you have available to you. For example, here @work, I have 3 versions of Perl (5.8.5/5.8.8/5.10.0) installed on 2 linux variants (32-bit/64-bit).

Perl::Tidy is another handy tool to guide new users on consistent code layout practices.

In reply to Re: Perl Test by toolic
in thread Perl Test by Faoahy

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.