Esteemed fellow monks,

Reviewing some of my Perl code, it just occured to me that I could "optimize" this expression: 

join '', $config{'prefix'}, $item, $config{'suffix'}

[download]
...into something shorter, like this: 
join $item, @config{'prefix', 'suffix'}

[download]

I still prefer the first version, however, as the second one tends to obfuscate the order of parts in the final result. It could inconvenience extension, too.

Of course, simple concatenation would be even more straightforward: 

$config{'prefix'} . $item . $config{'suffix'}

[download]
But I have no strong opinion there, since the join-tightly idiom seems commonplace enough to be recognized as equivalent. What do you think?

-martin

In reply to Perl style: Arguing against three-argument join() by martin

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.