And since we're using the pragma, we can also be more specific about which warnings we don't want. Then we can lose the prototype for errorchecking too (which it only does shoddily anyway). And lastly, undef is a one-element list and evaluates as true in list context, so we just let Perl decide what value the boolean expression should return.
sub is_opened { no warnings qw(closed unopened); return tell $_[0] != -1; }

Update: Oops. s/==/!=/ - otherwise the truth value is reversed of course. Thanks, blakem.

Update 2: and of course, check perldoc perllexwarn about the detailed warning names you can use to enable/disable specifically.

Update 3 (the neverending story): fruiture informs me that you have to disable not only the closed category, but unopened as well. Code updated accordingly.

Makeshifts last the longest.


In reply to Re^2: Filehandle open? by Aristotle
in thread Filehandle open? by maclypse

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.