Braces are a nice visual cue that make a filehandle variable instantly recognizable as a filehandle.

Guessed that I could whip up an example where it isn't? 

qwurx [shmem] ~ > perl -le '$h = {foo => "42"}; print {$h} "foo"'
Not a GLOB reference at -e line 1.
qwurx [shmem] ~ >

[download]

Aha.

sort {byid} @list;
map {$_->()} @stuff;
print {$fh||$ofh} @vars;

[download]

Braces are no nice visual cue! They mean and do something. Using them uncalled for is either decorative or cargo cult programming.

Note that I'm not averse to the odd drink which is style, I just don't call "best practice" any blurf which doesn't hold water.

In reply to Re^9: Split output by tabs (bogus best practice) by shmem
in thread Split output by tabs by perlnoobster

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.