comment on

Is there "a better way" to judge whether select works without having to fork and without it costing (too much) runtime?

This is as much a question as a suggestion.

On an OS where select does work on pipes, if you create a pipe, write to the write handle and then immediately select on the read handle with a timeout, shouldn't you get the read handle's fileno returned immediately? On Windows, you get 0:

pipe $in, $out;;

print $out 'fred';;

$si = ''; vec $si, fileno( $in ), 1;;

print select $si, undef, undef, 0.1;;
0 0.1
[download]

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: How to test for reliable select()? by BrowserUk
in thread How to test for reliable select()? by Lightknight

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks