[1/2] In #CommonLisp, SBCL accepts directory pathname components which are subpaths and not names:
(make-pathname :directory '(:absolute "tmp" "foo/bar")) returns #P"/tmp/foo/bar/".
On CCL, the same form yields #P"/tmp/foo\/bar/" which of course results in errors in a lot of contexts because "/" is not a valid character in filenames.
https://github.com/ciel-lang/CIEL?tab=readme-ov-file#docker
Build it, and you can run scripts with CIEL's batteries.
Next step would be you start Slime / your editor with a CIEL core image.
https://github.com/ciel-lang/CIEL?tab=readme-ov-file#docker
Build it, and you can run scripts with CIEL's batteries.
Next step would be you start Slime / your editor with a CIEL core image.
#Scheme elegant, academic
#Emacs lisp the only actually useful lisp
#clojure if it weren't JVM-based... there's always one bad apple
Installing lisp for beginners.
https://screwlisp.small-web.org/fundamental/installing-lisp-etc/
So much computing is predicated on having this or a conscious alternative decision to it. Here is my attempt to help beginners get this far. What do you think?
#commonLisp #emacs #beginners #lisp #programming #setup #software #developer
Installing lisp for beginners.
https://screwlisp.small-web.org/fundamental/installing-lisp-etc/
So much computing is predicated on having this or a conscious alternative decision to it. Here is my attempt to help beginners get this far. What do you think?
#commonLisp #emacs #beginners #lisp #programming #setup #software #developer
https://screwlisp.small-web.org/lispgames/LCKR-object-oriented-simulation-simulation/
I have to say, I am really, really happy with how the flow into the thirty second GIF reflects my ideal computer useage.
Basically, I write a clim command that steers my leonardo system "like a person does" via emacs-server, visible in the background of the straightforward clim interactor GUI I generated in a couple lines.
#Scheme elegant, academic
#Emacs lisp the only actually useful lisp
#clojure if it weren't JVM-based... there's always one bad apple
A great explanation by @vindarel of the differences between HANDLER-BIND and HANDLER-CASE in Common Lisp, and what it means that the former doesn't unwind the stack.
https://lisp-journey.gitlab.io/blog/lisp-error-handling-how-handler-bind-does-not-unwind-the-stack
A great explanation by @vindarel of the differences between HANDLER-BIND and HANDLER-CASE in Common Lisp, and what it means that the former doesn't unwind the stack.
https://lisp-journey.gitlab.io/blog/lisp-error-handling-how-handler-bind-does-not-unwind-the-stack
A few weeks ago I wondered what it takes to turn a small LISP-1 into a LISP-2. Turns out it takes just a few hours to get most things right, then some days to iron out a few subtleties, and then a couple of weeks to polish it into a piece of art.
MICRO COMMON LISP is a tiny, purely symbolic, microscopic subset of #CommonLISP. It runs in less than 64K bytes of memory, even on #DOS (tiny model) or CP/M. Here it is:
http://t3x.org/mcl/
#CPM#LISP
The Mini #CommonLISP I have been working on now runs on CP/M with 2416 free cons cells. Enough to load Ken Kahn's tiny PROLOG and run a few simple queries.
The #AgonLight (18MHz eZ80) loads the LISP part of the code (236 lines) in 11 seconds. Simple programs run at acceptable speed, but slightly more complex PROLOG queries take minutes. 😊
#LISP#CPM#PROLOG#Z80
The Mini #CommonLISP I have been working on now runs on CP/M with 2416 free cons cells. Enough to load Ken Kahn's tiny PROLOG and run a few simple queries.
The #AgonLight (18MHz eZ80) loads the LISP part of the code (236 lines) in 11 seconds. Simple programs run at acceptable speed, but slightly more complex PROLOG queries take minutes. 😊
#LISP#CPM#PROLOG#Z80
Just a heads up on these aggregators of Lisp blogs. If you have a blog that meets the requirements I encourage you to submit it.
Planet Lisp (Common Lisp)
https://planet.lisp.org
Planet Scheme (Scheme)
https://planet.scheme.org
[Common Lisp considered a dumpster.]
Since Alex responded, it's not worth adding more, but still, some of Dmitry Non's points do appear in plain text in Steele's book.
For example, that prog' came first and later it was decomposed into block', let', and tagbody'.
By the way, I had a need for progv' once and I was writing something simpler than an interpreter.<br/>Maybe it was a macro (so a nanocompiler, then).<br/>I find prog1' handy often; `prog2', maybe once.
Dmitry Non posted on what he finds weird or impractical in Common Lisp:
https://nondv.wtf/blog/posts/common-lisp-is-a-dumpster.html
and Alex wrote a response:
https://nytpu.com/gemlog/2025-06-01
For perspective on certain design decisions it helps to immerse in the historical context in which those decisions make more sense. I disagree with Alex that early Lisp dialects died out: @interlisp is alive and well
Every time I reread the classic Tutorial on Good Lisp Programming Style by Peter Norvig and Kent Pitman @kentpitman I discover and learn something new. It's dense with insight.
A space for Bonfire maintainers and contributors to communicate
