[Win32utils-devel] rb_w32_select function patch
Daniel.Berger at qwest.com
Wed Apr 30 10:45:04 EDT 2008
> -----Original Message-----
> From: win32utils-devel-bounces at rubyforge.org
> [mailto:win32utils-devel-bounces at rubyforge.org] On Behalf Of
> Heesob Park
> Sent: Tuesday, April 29, 2008 3:33 AM
> To: Development and ideas for win32utils projects
> Subject: Re: [Win32utils-devel] rb_w32_select function patch
> 2008/4/29 Luis Lavena <luislavena at gmail.com>:
> > On Tue, Apr 29, 2008 at 2:53 AM, Heesob Park
> <phasis at gmail.com> wrote:
> > > Hi,
> > >
> > > [snip]
> > > I added some safe check code.
> > > Here is diff -u output:
> > >
> > Hello Park,
> > I just tested your patch for rb_w32_select and found, even
> gets() is
> > no longer blocking other threads from being executed,
> everything stops
> > when you start typing something...
> > Compared to other other platforms, the behavior differs, so
> maybe is
> > not the best solution...
> > I thought your previous patch (2005, 2006 maybe?) workaround that
> > issue. But don't remember quite right.
> That patch is not working well as you expected.
> > In any case, this looks good, one step closer :-)
> > (btw, platform i386-mingw32)
> Here is a modified version for two step closer :)
The only difference I see between this and a Unix version is that
anything I type on the command line doesn't appear until I hit the Enter
key. On Unix (or with Jruby on Windows), I see whatever I type on the
console right away. I'm guessing it's a cmd.exe or native thread issue.
It's nothing big, but I thought I'd mention it.
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
More information about the win32utils-devel