Hi, Anton
No, the form passed to SOCKET-STATUS *DO NOT* depend on READY-ONLY (note: it's
READY-ONLY, not READ-ONLY).
Actually, all your patch does was the status updating "after" CLISP's
SOCKET-STATUS returned. This means, if a socket do have some inputs are
waiting for read, CLISP's SOCKET-S
10.04.2011, 18:39, "Chun Tian (binghe)" :
>
> believe this also closed another open issue reported by other users
> on Hunchentoot mailing list, in which they have to disable the use
> of READY-ONLY argument when calling WAIT-FOR-INPUT.
Dos the form of the argument passed to the CLISP function
10.04.2011, 18:39, "Chun Tian (binghe)" :
> Hi, Anton
>
> Thank you very much for looking into this issue and finally fixed it!
> I believe this also closed another open issue reported by other users on
>Hunchentoot
> mailing list, in which they have to disable the use of READY-ONLY
> argument
Hi, Anton
Thank you very much for looking into this issue and finally fixed it! I
believe this also closed another open issue reported by other users on
Hunchentoot mailing list, in which they have to disable the use of READY-ONLY
argument when calling WAIT-FOR-INPUT.
Any way, I've merged you
Hello.
I am using usocket 0.5.0 and it has a bug for CLISP.
In the function wait-for-input-internal there is a do* cycle which analyzes
the result of the CLISP function socket-status
(its docs are here: http://www.clisp.org/impnotes/socket.html#so-status)
Here is how the cycle is written now:
