Re: [clisp-list] socket-streams vs. two-way streams

[Todd S. <ta...@we...>]

Sam Steingold <sd...@gn...> writes:

> > * In message <m3d...@je...>
> > * On the subject of "Re: [clisp-list] socket-streams vs. two-way streams"
> > * Sent on 10 Jan 2002 23:19:09 -0500
> > * Honorable Todd Sabin <ta...@we...> writes:
> >
> > > > Also, is there a reason that it should only work with socket-streams?
> > > > Wouldn't it be a good thing for it to work on pipe-io-streams, too?
> > > > (Perhaps it already does, I haven't checked.)
> > > 
> > > please do check.  i believe it should work.  if it doesn't - send a
> > > patch.
> > 
> > It doesn't work.  It complains that it's not a socket-stream.  No
> > patch at the moment, maybe later.
> 
> please note that select() is a socket-specific syscall on win32, so you
> cannot pass just any handle to it.
> if you can make it work - great!

I don't think this is a (clean) way to make it work on win32.  Would
you take a patch which makes socket-status work on pipe streams on
linux/unix only?


Todd