[usocket-devel] Problem with :ready-only

[Daniel Weinreb]

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