December 2025 - pro - mailman3.common-lisp.net

GO stuff
by Marco Antoniotti 27 Dec '25

27 Dec '25

Hello I did not mention GO out of context in my previous emails. I would like to know the opinion of this forum about what would be the most likely CL - portable - substitute to implement *channels*. *usocket *and/or *bordeaux-threads* are what I'd target. In GO you have *chan *items and you can send and receive from them using the *<-* operator. AFAIU these channels are blocking. Any suggestions? Thanks Happy Holidays Marco -- Marco Antoniotti, Professor, Director tel. +39 - 02 64 48 79 01 DISCo, University of Milan-Bicocca U14 2043 http://dcb.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY REGAINS: https://regains.disco.unimib.it/

8 18

READ-SEQUENCE and USOCKET
by Marco Antoniotti 18 Dec '25

18 Dec '25

Hi I am reading from a uosocket:stream-usocket. My sequence is 100 octets long, but I know the other party is sending UP TO 100 octets. If the other party sends less than 100 octets, read-sequence/usocket-stream (at least the version on LW) hangs. Should I just do a loop, checking for the "end marker"? Thanks All the best -- Marco Antoniotti

10 26

Re: READ-SEQUENCE and USOCKET
by Marco Antoniotti 18 Dec '25

18 Dec '25

Thank you Vibhu That is exactly what I came up with, and it seems to work decently well. Only thing, I put a non-zero timeout. All the best Marco On Thu, Dec 18, 2025 at 10:18 AM Vibhu Mohindra <vibhu.mohindra(a)gmail.com> wrote: > -------- Forwarded Message -------- > Subject: Re: READ-SEQUENCE and USOCKET > Date: Thu, 18 Dec 2025 10:14:57 +0100 > From: Vibhu Mohindra <vibhu.mohindra(a)gmail.com> > To: pro(a)common-lisp.net > > How are you doing Marco? > > I'm looking at usocket-0.8.4. It may be worth exploring some of these > aspects I see in its code: > 1. option.lisp allows: (setf (socket-option mysocket :receive-timeout) ...) > 2. usocket.lisp defines a generic socket-receive. It's only implemented > for > UDP sockets but I don't see why it shouldn't be implementable for > stream-sockets too. > > Otherwise I don't see a better solution in usocket than inefficiently > checking for and reading a byte at a time, like this. > > (defun read-available-vector (vector socket &key (start 0) (end nil)) > "Reads whatever is presently available in SOCKET without hanging. > SOCKET and VECTOR are assumed to have elts of type (unsigned-byte 8). > Returns first unwritten position in VECTOR and whether at end-of-file." > (when (null end) (setq end (length vector))) > (assert (<= 0 start end (length vector))) > (flet ((socket-readyp () > (wait-for-input socket :timeout 0 :ready-only t))) > (do ((i start (1+ i))) > ((or (>= i end) (not (socket-readyp))) > (values i nil)) > (let ((b (read-byte (socket-stream stream) nil nil))) > (unless b (return (values i t))) > (setf (aref vector i) b))))) > > -- > Vibhu > -- Marco Antoniotti, Professor, Director tel. +39 - 02 64 48 79 01 DISCo, University of Milan-Bicocca U14 2043 http://dcb.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY REGAINS: https://regains.disco.unimib.it/

2 1

leave
by B. Mansurov 17 Dec '25

17 Dec '25

2 1

Correction of Georgiy's name, contact info for him
by David Cooper 17 Dec '25

17 Dec '25

Apologies to Georgiy for working from my (apparently failing) memory and neglecting to take a few seconds to look up his last name, which is Tugai, not Tsukai. I wanted to make sure he gets recognized for all his work. Anyone wishing to contact him, let me know and I'll put you in touch, he's active on IRC, I won't presume to dox him any more on these lists, but anyone wishing to contact him let me know and I'll put you in touch (he is on mailto:clo-devel@common-lisp.net as well). Dave

1 0

*load-pathname* and *compile-file-pathname* issues
by Marco Antoniotti 16 Dec '25

16 Dec '25

Hi I am getting old and I get confused. Here is the thing (a followup to the "wild" ASDF module question). I am writing something that will have, at run time, a variable * the-directory-where-stuff-is*. Now, I want to initialize this variable automagically, with no "outside" references. I thought I could do something like (defvar the-directory-where-stuff-is* (merge-pathnames (make-pathname :directory '(:relative "stuff") :name nil :type nil) (make-pathname :name nil :type nil :defaults *load-pathname*))) Alas, ASDF and other things may move the compiled file to a cache folder, which, in the end misaligns *load-pathname* w.r.t. where "stuff" actually is (and should be). This is something that build systems like cmake achieve with the notion of "source", "install", etc folders. Any ideas, suggestions, incantations, workarounds, even at the ASDF level to get this done? Thanks -- Marco Antoniotti

7 13

Loading the content of a "data" directory with ASDF (vel similia)
by Marco Antoniotti 01 Dec '25

01 Dec '25

Hello parenthetically unchallenged friends! Suppose I have a library that is structured as src/ code.lisp pkg.lisp stuff.lisp data/ data-file-1.lisp data-file-2.lisp data-file-3.lisp ... data-file-3-point-14-godzillion.lisp Actually, the data folder could be anywhere. How do I tell ASDF (or similar) to just slurp in all the data files at once? I know it's doable, but maybe someone knows of a better way. Thanks Marco -- Marco Antoniotti, Professor, Director tel. +39 - 02 64 48 79 01 DISCo, University of Milan-Bicocca U14 2043 http://dcb.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY REGAINS: https://regains.disco.unimib.it/

6 7

Testing
by Burton Samograd 01 Dec '25

01 Dec '25

Hi All, Just a test message to see if I can get through. -- Burton Samograd

2 1