Graff,

To answer your first question, try:

perl -e 'undef $!; print "just kidding\n" if defined $!'

This prints "just kidding" on AIX 5.2 (perl 5.8.0 and 5.005_03), cygwin (perl 5.8.7), linux 2.4.2 (perl 5.6.0), Solaris 5.9 (perl 5.6.1, 5.6.0, 5.005_03).

What I'm looking for is general advice which allows me to add error checking to all my calls to readline or <$fh>. Here are my "requirements": a minimal amount of ugly code, relatively efficient, independent of the rest of my program (that rules out using the "send STDERR to scalar" trick). It would also be nice if the technique worked at least as far back as perl 5.005_03.

$fh->eof is best avoided if $fh might be attached to a terminal, which in the general case it might be.


In reply to Re^2: Best way to handle readline errors? by jrw
in thread Best way to handle readline errors? by jrw

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.