Sorry, these code is NOT written by me, it's by Erik Huelsmann. I just
confirmed them when I was adding UDP support to WAIT-FOR-INPUT-INTERNAL.
--binghe
> Hi, Anton
>
> Thank you very much for your patient explanation, now I completely understand
> this:)
>
> The USOCKET SBCL/win32 supporti
Hi, Anton
Thank you very much for your patient explanation, now I completely understand
this:)
The USOCKET SBCL/win32 supporting code is port from LispWorks/win32 supporting
code, this is how LispWorks do the same work:
(defun free-wait-list (wl)
(when (wait-list-p wl)
(unless (nul
"Chun Tian (binghe)" writes:
> I think I cannot understand why the closure must close over those
> components of WAIT-LIST but WAIT-LIST itself, but since this is a fact
> (as you confirmed), I'd like to adopt your patches and quote all your
> explanations and put with the new code together. I h
Hi, Anton!
Thank you very much. Actually I just realized that you're the author of
sbcl-win32-threads. Among other things, I want to say how important your
packages are, because I know there's a commercial Lisp-based product (Gensym
G2) which heavily depends on SBCL/win32 (for development, th
Greetings to all USOCKET developers and contributors.
First, thank you for the wonderful package. But of course, I'm posting
here to report some problems (on a particular platform: #+(and sbcl win32))
1. Event handles are leaking in current SBCL backend implementation,
because of SBCL-unfrien
