Here's the thing...

I've got a socket, created with IO::Socket::INET, that I've registered with an IO::select object.

I'm writing to the socket using the following code:

if (my @s = $select->can_write()) { for (@s) { if (print $_ $message) { print "message sent"; } else { print STDERR "Could not write to socket: $!\n"; } } }
I only have one socket registered with the select, so it only writes to the one socket. This code works fine, except...

The server I'm talking to has the annoying habit of terminating the connection with no warning. When that happens, the $select->can_write() is not blocking, but immediately returns the one registered socket (which was closed from the other end), and the print fails.

Is can_write() supposed to return a handle that I clearly cannot write to? If so, what suggestions can I get for bulletproofing my code?


In reply to Stupid IO::select question by BlaisePascal

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.