My belief is that, on unix, $! mirrors errno exactly. And on unix, errno behaves the way I have described. It is modified (to a non-zero value) by failing system calls and not modified by successful ones. Therefore, on unix, setting $! to zero before making a call to a perl function which (may) make a system call is a valid way of checking for an error.

Can anyone explain why Windows perl behaves as it does, and not like unix, in this respect?

In any case, using readline on Windows seems like a very iffy proposition if you're doing any serious programming which requires tight error checking. I wish that weren't so, because readline certainly is convenient.

In reply to Re^10: 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.