freenode/#lisp - IRC Chatlog
Search
21:24:41
drmeister
Im thinking aloud here while I’m on my phone - can I define a method on finish-output for a stream? Python has a sys.displayhook() that I need to mimic so that cl-jupyter can display intermediate output
21:29:29
Shinmera
https://github.com/trivial-gray-streams/trivial-gray-streams/blob/master/package.lisp#L36
21:29:52
Shinmera
subclass the appropriate output-stream class, and add a method to stream-finish-output
21:37:04
Shinmera
You could base it on the redirect-stream for instance https://github.com/Shinmera/redirect-stream
22:27:06
grobe0ba
i am having issues running CCL. On Alpine, with MUSL libc, i'm missing symbols, which is to be expected, so i'm not bothering with that at the moment. however, since that fails, i have been attempting to run it in a docker container with centos, which fails with "Couldn't load lisp heap image from /home/grobe0ba/opt/ccl/lx86cl64.image: Operation not permitted".
22:27:40
grobe0ba
the container is privileged, using host networking, and has multiple add-caps, all apparently of no use.
23:01:35
pillton
stylewarning: Regarding the conversation a while back where you said: "ad hoc polymorphism is nice with types/classes/CLOS/spec-store/whatever, but I meant parametric polymorphism above, where we define a function that's singly generically useful for many types"
23:02:15
pillton
stylewarning: I attempted to do that with https://github.com/markcox80/template-function which is built on top of specialization store.
23:35:31
Fare
stylewarning, pillton, have you seen lisp-interface-library, for parametric polymorphism?
0:33:14
pillton
Actually, what I really mean, I had difficulty mapping lisp-interface-library to the problems I have.
0:34:08
stylewarning
LIL to me was the introduction of a new paradigm to Common Lisp, not a library to fulfill the needs of an existing paradigm
0:35:12
stylewarning
it does enable different sorts of polymorphism, but doesn't map syntactically to any usual way of thinking about polymorphism (imo)
0:35:41
stylewarning
Haskell type classes, for instance, eventually map to an interface-passing style mechanism under the hood, but it's not something you ever see or are exposed to as a user
0:56:20
PuercoPop
Fare: looking into the quake source code I see some code for the alloy-mode, but I'm unsure what was the use case of alloy, to help model the DB?
3:26:41
PuercoPop
At long last my XCB client can send and read the setup request. Now I have to think how to reify the XCB types, probably as CLOS classes. I've seen the Elisp client uses the slots in a class as 'schema' but one can't assume the slot order is they are 'written in code' right? Plus I don't want to keep the padding bytes in slots if I can avoid it.
3:31:42
sabrac
Agree the slot order is not specified, so you cannot rely on the order in the written code
3:33:51
PuercoPop
I've been thinking of maybe writing the schema filter padding fields before defining the corresponding class