read changed to blocking in 1.9 windows?

[Roger Pack]

Currently with 1.9 if you do a
#include<ruby.h>

by default it overwrites any calls to 'read' and 'accept' (etc.) to be
rb_w32_read, rb_w32_accept (etc).

This worked all right in 1.8.6.
However, with 1.9 it would appear that inexplicably rb_w32_read, if it
would block (i.e. no data) blocks now, until data is ready. Thus
rb_w32_read behaves differently than the old read used to, and
differently than the way linux' read does.
Is this a bug? I assume it is?
Thanks.
-=r

 

[Robert Klemme]

Currently with 1.9 if you do a
#include<ruby.h>

by default it overwrites any calls to 'read' and 'accept' (etc.) to be
rb_w32_read, rb_w32_accept (etc).

This worked all right in 1.8.6.
However, with 1.9 it would appear that inexplicably rb_w32_read, if it
would block (i.e. no data) blocks now, until data is ready. Thus
rb_w32_read behaves differently than the old read used to, and
differently than the way linux' read does.
Is this a bug? I assume it is?
Thanks.

Maybe that's a side effect of using real threads in 1.9. In that case
using blocking IO might be OK.

Kind regards

robert