libera/#commonlisp - IRC Chatlog
Search
3:50:39
hayley
I'd be interested in any other GC-heavy multi-threaded benchmarks too, for what it's worth.
4:05:20
jmercouris
borodust: is it called 'burgled batteries' because the batteries are burgled from other projects? is that the rationale?
4:06:40
jmercouris
borodust: sorry, I confused you with somebody else, I was thinking of bodge* or some other library you have and burgled-bodged got transposed in my head
4:40:34
etimmons
So I've always assumed that it's called "burgled batteries" since, as a Python/CL bridge, it's stealing Python's batteries
4:41:37
jmercouris
I kind of want to make my own lisp which is a superset of Common Lisp by including some of my favorite CL libraries
4:42:09
jmercouris
I wouldn’t make a new compiler or anything, just ship an image with some libraries added
4:43:54
hayley
Because another language breaks compatibility with everything, whereas just having "CL with some nice libraries" doesn't.
4:44:28
hayley
Yeah. Good chance that (defpackage :blah (:use :cl)) is going to do something very bad.
7:18:55
jackdaniel
yesterday I wrote a short post about the macro do and tail recursion https://turtleware.eu/posts/How-do-you-DO-when-you-do-DO.html
7:19:07
jackdaniel
that was prompted by the yesterday discussion about do (however only remotely relevant to it)
7:33:21
jackdaniel
I don't have any strong preference - if something can be expressed clearly in terms of do then it is fine
7:33:41
xaotuk
jackdaniel: Wow! I always observed "do" as some ancient iteration construct, never being aware that it's compact tail recursion. You opened my eyes, thanks!
8:49:37
Colleen
borodust: drmeister said at 2021.10.11 20:25:12: Thanks - I wasn't sure if I was just not thinking about it properly
11:08:13
skeemer
hello all, i am quite new to common lisp, i was wondering why most of the people uses sbcl, and what are the reasons to prefer it to clisp ?
11:09:18
hayley
SBCL compiles to machine code, so it is (almost?) always faster, and it is more maintained.
12:38:09
icer
My working remote slime/swank debugging broke after trying to update sbcl to the downloaded latest from Ubuntu 20.04's default. I've tried reverting, recompiling, but now it's always complaining about swank-io-package stuff missing and swank indentation things missing. Any ideas?
12:45:55
beach
icer: You can use completion to get the full IRC handle of the person you are addressing.
12:51:34
icer
jackdaniel: Ok, I can connect to the binary running on my local machine, but to the same binary over ssh port forwarding, the same errors occur.
12:55:50
icer
jackdaniel: I md5summed the binary to confirm its the same. There is no ~/.slime on the remote system.
13:01:17
_death
jackdaniel: when I think of DO, I tend to recall the little box on PG's ANSI Common Lisp, I think with the headline "The point of DO".. in it he quotes from the paper "The Evolution of Lisp"
13:03:26
icer
I still connect and get the "Can't locate module: SWANK-IO-PACKAGE::SWANK-INDENTATION", which is odd considering it's the same binary.
13:03:56
_death
the quotation is about how iteration over a single variable is often not very useful on its own, and how DO allows iterating multiple variables, and consequently the DO body can often be empty
13:07:40
_death
icer: a while ago I added a restart to be able to continue from this error, btw.. https://github.com/death/slime/commit/9f5cc8c7cf042f821ee3f2c838c6b617e8aeaf6d
13:09:53
icer
_death: nice retart idea. So, are fasls not built into the image? My Makefile uses (asdf:make). Or is swank something I need to manually quickload on the remote?
13:14:56
icer
_death: I don't do an explicit load, just a ql:quickload of the project's asd system, then build, which shouldn't call the entrypoint. At one point I tried adding --eval '(swank-loader:init)' before the build command.
13:33:57
icer
_death: It takes a couple minute to deploy - slow connection. In the meantime I tried sshing in to the remote and trying to emacs/slime locally on the remote and got a swank version mismatch 24 vs 26.1, which apt tells me 24 is on the remote, and I know 26.1 is local to my dev machine. May be the issue.
13:43:36
icer
_death: how do I make slime recompile after I patch the file for your restart? I did a slime C-c C-c, and compiled, but that didn't seem to be enough.
13:46:46
icer
_death: odd, the swank-loader line doesn't seem to have an effect, the remote is still looking for the v24 swank rather than what I tried to build into the image.
13:53:38
icer
_death: yes, I forgot to "purge" it, I'll see if that works. I've also quickloaded swank, but that didn't work.
14:17:44
icer
_death: so.. same as dev machine, used quicklisp to install swank and melpa in emacs to install slime on remote. Tried using emacs/slime on remote for a remote-local connection, and it fails, same failure to load swank-indentation :(