Mine is similar to the op. Telling built ins that take a list where the list ends. 
my %broken = (
  monday  => join q{/}, q{one}, q{two},
  tuesday => sprintf q{%s%s}, q{three}, q{four},
);

my %better = (
  monday  => join(q{/}, q{one}, q{two}),
  tuesday => sprintf(q{%s%s}, q{three}, q{four}),
);

[download]
Rather than have to remember that parens are needed in this case I tend to use them all the time. If the function's args are on more than one line it gives you something to pin the ; to. 
my $str = sprintf(
  q{%s -> %s},
  get_data(),
  get_more(),
);

[download]

In reply to Re: your Perl bug Achilles heel by wfsp
in thread your Perl bug Achilles heel by perrin

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.