What on earth would generate a read failure? You mention reading a directory. Yet, directories are just regular files that have special magic associated with them at the OS level. Linux does a little more work for you than Solaris does. This fact doesn't surprise me at all. Personally, I think Solaris is an OS that hasn't been intelligently supported in years and am actively trying to convert my company from Solaris 2.9 to RH ES 3.

That said, I'm still wondering what other situations would generate a read failure. If you can successfully open a file, you should always be able to read from it. Of course, I suppose you could create the file, open it successfully, then delete it and try to read from it. That might generate a read error. Then again, a simplistic test on Cygwin(WinXP) didn't. I suffered from input buffering. *shrugs*

Good luck?

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

In reply to Re: Testing for read() failures on different platforms by dragonchild
in thread Testing for read() failures on different platforms by leriksen

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.