I wonder about this also. Annoying to kind of have to convert that in your head when reading older style instruction (Network Programming with Perl by Stein) that use barewords all over the place when the newer guidance is to use lexical filehandles. I think that the short answer is that the bareword is the old way to do it, and now you should use lexical variables because they limit the scope. This seems to confirm: 
#!/usr/bin/env perl
use strict;
use warnings;

{
open (OUTPUT,"> out.txt") or die;
}

print OUTPUT "a"; # Works OUTPUT must still be in scope

{
open (my $new_out, ">","new_out.txt") or die $!;
print $new_out "b";
}

#print $new_out "c"; #this will not work

[download]

In reply to Re: Why don't file handles have sigils? by trippledubs
in thread Why don't file handles have sigils? by 1s44c

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.