Hi,

At Thu, 1 Aug 2002 16:35:25 +0900,
Matt Pattison wrote:
> The problem with my program is that (in Windows) gets seems to block the entire
> process rather than just the current thread. This program works as expected in
> linux, with the poll and process threads running continuously whilst the input 
> thread is waiting for user input. In windows however all threads appear to halt
> as soon as the gets line is reached in the input thread, and only continue once 
> user input has been given. Can anyone help?   

This limitation comes from that the current implementation uses
select() in winsock.  It works only for socket handles, so the
others are treated as always immediately readable/writable.
This problem has been known but still unsolved.

And one more issue, windows console reports ready to I/O even
when a mouse event occurs, but ruby doesn't want it.

-- 
Nobu Nakada