From: Francis Cianfrocca <garbagecat10@...>
Date: 2006-10-24T01:42:01+09:00
Subject: Re: Trouble using puts and getc in different threads

------=_Part_93267_20127243.1161621719699
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 10/23/06, Jan Svitok <jan.svitok@gmail.com> wrote:
>
>  if you're on windows, see [1] thread for a solution, especially [2]
> (using kbhit()) and
> [3] (using select)
>
> [1] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/204589
> [2] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/204863
> [3] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/205002
>
>


I'm still wondering what the problem with #getc is. Is it possible that the
way Ruby implements it is not interruptible in Windows, so Ruby can't run
the thread scheduler around it?

------=_Part_93267_20127243.1161621719699--