The bug doesn't happen because perl has STDIN line-buffered. Select won't notice STDIN has read data until you press enter. This also means there will always be a newline to read for <STDIN>.

sysread will give you the unbuffered activity you expect but select will not. I think this is where you are mistaken. This means select will still be blocking until you press enter. I was able to get select to trigger on a single character by using tcsetattr to disable line-buffering (aka canonical mode) for the terminal. (code at the end of the post)

edit: Just to be clear about what this implies, this leads me to believe that line-buffering happens at a lower level than the perl interpreter. This answers your rhetorical question:

How can the select system call know that Perl has data waiting to be read in a buffer?

It is my hypothesis that the buffer you speak of happens at the system level and not inside the perl interpreter. Using stdio.h functions like getc and getline, you must read input through the terminal's internal buffer while in canonical mode. The read system call (via perl's sysread) does not use this higher-level terminal line buffer.

I have no idea how this works in windows. 

#!/usr/bin/env perl

use warnings;
use strict;

use IO::Select;
use IO::Handle;
use Inline 'C';

my $select = IO::Select->new( \*STDIN );
disable_canon_mode() if @ARGV;
# Experiment by commenting out the above line and giving command-line
# arguments.

while ( 1 ) {
    $select->can_read; # block until new input
    warn "CAN_READ STDIN\n";

    my $in;
    if ( @ARGV ) {
        sysread STDIN, $in, 1;
        print "Char read: $in\n";
    }
    else {
        $in = <STDIN>;
        print "Line read: $in\n";
    }
}

__END__
__C__

#include <termios.h>

#define STDIN 0

void disable_canon_mode ()
{
    struct termios tio;

    if ( isatty( STDIN ) == 0 ) { return; }

    /* Turn off canonical mode, meaning read one char at a time.
       Set timer to 0, to wait forever. Minimum chars is 1. */

    tcgetattr( STDIN, &tio );
    tio.c_lflag &= ~ICANON;
    tio.c_cc[ VTIME ] = 0;
    tio.c_cc[ VMIN  ] = 1;
    tcsetattr( STDIN, TCSANOW, &tio );
}

[download]

In reply to Re^3: Non-blocking I/O woes by juster
in thread Non-blocking I/O woes by dwalin

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.