Hi Mihai,
On Wed, Dec 16, 2009 at 12:00 PM, Mihai Bazon wrote:
> Hi folks,
>
> What's with the ready-only arg to wait-for-input? It's not documented
> anywhere, but I noticed that if I don't pass T for it my code behaves
> strangely.
Without the READ-ONLY arg, WAIT-FOR-INPUT will return all soc
Hi Erik,
Thanks for the reply! It does explain why my code doesn't work well
without passing :READY-ONLY T (it probably tried to read from sockets
that weren't ready, thus blocking the thread).
It's a pity that this arg is undocumented, and it should really be T by
default (with NIL it defies th
Hi folks,
What's with the ready-only arg to wait-for-input? It's not documented
anywhere, but I noticed that if I don't pass T for it my code behaves
strangely.
Cheers,
-Mihai
___
usocket-devel mailing list
[email protected]
http://common-l