I'm using 5.6 and I cannot find the behavior you allude to for select. I believe it returns (and always has) the number of file descriptors available for I/O or with events select is set to detect. AFAIK, that is the only return value for select.

( the UDP socket ) blocks if the UDP buffer has been emptied

I assume you mean that reading on the socket blocks if it is empty. You should be able to read the UDP socket to see if there is data on it. With fcntl's F_SETFL and O_NONBLOCK set, you should be able to read the socket until there is nothing to read. I have done this more than once on *nix systems with UDP sockets and IO::Select.

HTH, --traveler

In reply to Re: IO::Select vs select function by traveler
in thread IO::Select vs select function by geektron

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.