That said, I'm still wondering what other situations would generate a read failure.

Very true, we've been discussing that here - more like, well, if it 'very rarely' happens, should we try to catch a failure.

But seeing as we have code that tries to deal intelligently with this scenario, we really should try and test it, just to confirm the code really does what we think it does.

So yes one solution is to not cater for read failures on successfully opened files - then you dont need a test case !-)

But we are (currently) catering for it, and we want to test that accomodation on different platforms - but with the above mentioned difficulty.

FWIW, we are getting a consistent (as in, the same error message) on Linux and Solaris if we replace the dummy directory handle (made with IO::File) with one created by IO::Dir - we get 

'usage: $dh->seek(POS) at ...'

[download]
on both platforms - so that would work for now, but come the day we go to another platform I dont hold much hope that will be robust enough

+++++++++++++++++
#!/usr/bin/perl
use warnings;use strict;use brain;

In reply to Re^2: Testing for read() failures on different platforms by leriksen
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.