I think I agree almost entirely with this; however I can't help but feel that Perl in its current form is set up to allow idioms for almost any "simple" task.

The mere existance of variable "shortcuts" such as $/ and the like enables a whole host of one-liners, especially when coupled with $_, @ARGV and <> - almost certainly at the expense of code readability.

I think care needs to be taken whereever idioms are used - especially with code that others are going to have to maintain - the same care that should be taken when writing any code to ensure that it's readily understandable.

Future maintenance is the key - if it's not clear what it does, it's not going to be easy to maintain, in my opinion.

--Foxcub

In reply to Re: Idioms considered harmful by Tanalis
in thread Idioms considered harmful by rinceWind

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.