fraca7 wrote:
Jonathan Fine a écrit :
Paul Rubin wrote:
As I recall, some posts to this list say that Windows provides
non-blocking i/o for sockets but not for files.
No, Windows does provide non-blocking I/O for regular files, but it's a
completely different mechanism than the one used by winso
Jonathan Fine a écrit :
Paul Rubin wrote:
As I recall, some posts to this list say that Windows provides
non-blocking i/o for sockets but not for files.
No, Windows does provide non-blocking I/O for regular files, but it's a
completely different mechanism than the one used by winsock. You'll have
Paul Rubin wrote:
Jonathan Fine <[EMAIL PROTECTED]> writes:
My question is this: Under Windows, is it possible
to read as many bytes as are available from stdout,
without blocking?
I think Windows implements non-blocking i/o calls. However the
traditional (to some) Python or Java approach to this
Jonathan Fine <[EMAIL PROTECTED]> writes:
> My question is this: Under Windows, is it possible
> to read as many bytes as are available from stdout,
> without blocking?
I think Windows implements non-blocking i/o calls. However the
traditional (to some) Python or Java approach to this problem is
Hello
I have written a program that interacts with a
command line program.
Roughly speaking, it mimics human interaction.
(With more speed and accuracy, less intelligence.)
It works fine under Linux, using select().
But Windows does not support select for files.
Only for sockets.
Here's a google se
