wait-for-input does not work

Hi.  I just tried out the latest usocket, and found that
wait-for-input does not work properly.  To fix it, I changed the
default value of the :read-only parameter from nil to t.

What's going on with the :read-only parameter?  No function in usocket
passes this argument to wait-for-input.

Thanks.

-- Dan

Problem with :ready-only

Hi. I just tried out the latest usocket.  It's not working
properly for me, because wait-for-input returns true
even when there isn't any input.

If I change the default value of the :ready-only argument to
wait-for-input to t instead of nil, that fixes the problem.

I don't even understand why this argument
exists; no caller seems to pass it at all!  What's going
on here?

Thanks.

-- Dan

[Patch]: Clisp can't find gethostname on Linux

I attached a patch which allows Clisp to find gethostname on Linux.

--

-- 
With Best Regards, Stas.

_______________________________________________
usocket-devel mailing list
usocket-devel@...
http://common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel