Thanks, ikegami! That was useful.

It's worrying that <$fh> won't return when you eject and/or reinsert the media. What's going on down in the bowels of that code?

sysread and read were planned in a way which takes errors into consideration (patterned after read in c). But error handling in readline seems to be somewhat of an afterthought. It makes me wonder if I have to reimplement readline at the perl level using read (Ugh!).

I started asking this question because it's hard for me to justify writing code which will run as root that doesn't have complete error checking, including checking for input errors. Oh, Damian, why didn't Perl Best Practices should us lowly monks how to handle readline errors, too?

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.