Yes, the test suite now passes the tests for this.
My application still breaks as reported in my other emails, so it's a little
hard to test this on my real code.
Thanks!
2011/5/1 Chun Tian (binghe)
> Hi, Elliott
>
> I believe this bug was now fixed. The third WAIT-FOR-INPUT in your test
> co
Hi, Elliott
I believe this bug was now fixed. The third WAIT-FOR-INPUT in your test code
shouldn't return a non-NIL value, but a bug in function WAIT-FOR-INPUT caused
the "last" status of sockets didn't been reset correctly.
This bug only affect SBCL and ECL on Windows, and was fixed in r653 o
Hi, Elliott
Thank you, I've installed this SBCL binary and merged your test code into
usocket's unit test [1]. And Yes, I can see the BAD-FILE-DESCRIPTOR-ERROR now.
This happens only on SBCL/Windows but other platforms. I also tried your test
code on other CL implementations, it passed on most
By the way (in case you have any trouble reproducing), the version of SBCL
used to test this can be obtained here. (It's just a more up-to-date version
than what you can get on the SBCL download page that I compiled myself.
http://elliottslaughter.net/files/sbcl-1.0.46.msi
2011/4/30 Chun Tian (bi
Hi, Elliott
Sorry for late responses, I'm a little busy in the past week.
It seems that current implementation of WAIT-FOR-INPUT on SBCL/Windows have
some bugs, I'll look into it in next two days and try to fix it. Whatever bug
it has, it shuold NOT be any bug in SBCL itself, because this func
