In your case, delete $ENV{_} is the same as delete $ENV{"_"}. But that doesn't mean file handles are illegal to appear inside hash brackets. Any expression may appear there. Perl will just evaluate that expression (in scalar context (list context when slicing)), and, if necessary, cast the result to a string.

print "$ENV{FOO}\n"; # FOO stil in environment!!!
Considering that the bareword FOO can also be a filehandle, you really do not want perl to warn if a (potential) filehandle is used as a hash index. How's perl to know that when you write FOO, you really meant FOO, but when you write _, you might have typoed $_?

In reply to Re: Why did this error slip through? by JavaFan
in thread Why did this error slip through? by rovf

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.