With freedom comes responsibility. Perl sets you free to program the way you want. If you abuse it you will pay. For example golfing down some code is fun but it doesn't lead to maintainable code.

I never use a CPAN module without first making sure that it is suitable for my needs. Most of the time the CPAN module works as advertised occasionally it doesn't. That's the beauty of Open Source. You trust no one. Always validate code you get from somewhere else. M$ languages on the other hand are take it or leave it. You can't validate their code because you don't have it. If there's a problem you can't check their code to see if that is causing it. You do it their way or you don't do it at all, at least in their view.

In reply to Re: TMTOWTDI... and most of them are wrong by NateTut
in thread TMTOWTDI... and most of them are wrong by tlm

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, 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
  • 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.