HELLO! My #opensource #lisp game Kandria is now out on GOG with a 70% discount (highest ever!) to go along with it:
#commonlisp
@amoroso @aartaka Standardized #lisp #commonlisp has a bunch of different embedded languages (LOOP -> macro-based transpiler, FORMAT strings -> interpreter and transpiler, CLOS -> extension of Lisp, ...). As libraries there are zillions more of those. Then CL inherits features from Lisp 1, Maclisp variants and has evolved from CLtL1, CLtL2, ANSI CL. One thing that is missing in the post: CL-USER . The CL-USER package contains an implementation specific largely extended version of Common Lisp.
This week's #commonlisp project:
Realistic test data generator.
Ever needed a realistic test data for your analysis project? Are you a teacher or student and looking for a realistic data source for exams or practicing? Or, are you developing a data visualization or data handling project?
generate-test-csv has your back.
Grab it here: https://git.sr.ht/~hajovonta/generate-test-csv
@momo cool!
Well then, please have a listen to the episodes of the #LispyGopherClimate podcast that me, @kentpitman and @screwlisp did these past few weeks:
- Kent Pitman presents his lisp condition system implemented for python
- Kent Pitman, Scott Zimmermann, Ramin Honary, Screwlisp: Lisp Conditions in Python
- Common Lisp condition handling lore
- Common Lisp condition system, code review of my programming example
- Common Lisp condition handling w/ Kent Pitman, Ramin Honary
#tech #software #Lisp #CommonLisp #Scheme #SchemeLang #R7RS #MITScheme #Guile #GuileScheme
Lem editor news: it just got the one shortcut that makes me a 10x developer: `lisp-call-defun` bound (as in Slime) to C-c C-y.
https://lem-project.github.io/usage/common_lisp/#call-the-form-at-point-lisp-call-defun-c-c-c-y
(this one is strangely absent from Sly)
@screwlisp @kentpitman I’m just reading up on the MIT-Scheme condition system. Recent efforts to standardize this are defined in SRFI-255: “Restarting conditions”.
An older standards condition systems in Scheme was defined in SRFI-35: “Conditions”. And #Guile users can use the Guile implementation of SRFI-35 to make use of it.
I wish I had known about this two weeks ago when we first started talking about it on the #LispyGopherClimate show, but better late than never, I guess.
#tech #software #Lisp #CommonLisp #Scheme #SchemeLang #R7RS #MITScheme #Guile #GuileScheme
Finally uploaded "Adaptive Hashing: Faster Hash Functions with Fewer Collisions" to arXiv for better visibility:
https://arxiv.org/abs/2602.05925
I’ve polished the presentation, fixed typos, and moved to a more readable format than the original ACM version. #HashTables #DataStructures #CommonLisp
@crmsnbleyd
CL-USER> (ql:system-apropos "xml")
#<SYSTEM bknr.xml / bknr-datastore-20100916-git / quicklisp 2010-09-16>
#<SYSTEM cl-libxml2 / cl-libxml2-0.3.4 / quicklisp 2010-09-16>
#<SYSTEM cxml / cxml-20100916-git / quicklisp 2010-09-16>
etc.
#quicklisp #commonLisp #packaging
My #lisp #symbolic #deepLearning #ffnn #condition streamlined.
https://screwlisp.small-web.org/conditions/lisp-symbolic-deep-learning-streamlined/
The pretty and overtly useable rewrite of my earlier brace of articles.
An important condition handling style mistake I cleaned up was that I had previously put HANDLER-BIND /inside/ my INFER. But this freezes it in place; I might as well have used functions as such. Now the algorithm graph is essentially the condition handlers and restarts outside the function at runtime.
Artyom Bologov @aartaka describes the languages and programming styles that are in Common Lisp. To me Common Lisp is more a rich toolbox than a family of languages.
@the_heruman
Hey, I wonder if you might be available to talk briefly about some of your interests on the Sunday-morning-in-Europe 8am Sunday UTC peertube live edition of the weekly podcast I do (e.g. with KMP and Ramin on the Tuesday-night-in-the-Americas edition last 0UTC Wednesday).
I am modestly well acquainted with #commonLisp diaspora of some of your interests myself. It would be very interesting to hear what you have been doing and are interested in in the wild recently (lisp or not).
Daniel Kochmański @jackdaniel is revising the manual of McCLIM, starting from the chapters on the development history and getting started.
From this I learned that in 2026 it has been 10 years since he took over maintenance of McCLIM. Thanks to Daniel and all contributors for their work on this great implementation of the Common Lisp Interface Manager GUI toolkit.
#lispyGopherClimate #lisp #technology #podcast #archive, #climate #haiku by @kentpitman
https://communitymedia.video/w/c3GdAXe7BQTbK3VrcXCm7E
& @ramin_hal9001
On the #climate I would like to talk about the company that found #curl and #openssl's #deeplearning many (10ish) 0-day vulns "using #ai ". (#llm s were involved).
This obviously relates to my #lisp #symbolic #DL https://screwlisp.small-web.org/conditions/symbolic-d-l/ (ffnn equiv). Thanks to everyone involved with that so far.
I implemented that using #commonLisp #condition handling viz KMP.
https://screwlisp.small-web.org/conditions/symbolic-d-l/
#Symbolic #deepLearning #inferencing with #commonLisp #conditions
The #DL from before, but it works via a mixture of condition handlers and restarts.
This turned out to be condition example boilerplate, but it was interesting to me personally, at least!
Not sure about this construction I used (paraphrasing):
(prog ((c nil))
start
(restart-case
(if c
(signal c))
(resignal (condition) (setq c condition) (go start))))
@me Yes, functionally equivalent. (lambda …) was a late addition to #CommonLisp to make it more compatible with #ISLisp
This tutorial on building a GUI application in Common Lisp with GTK and SBCL is not new but has just crossed my feeds, so it's new to me.
https://blog.matthewdmiller.net/learn-common-lisp-by-example-gtk-gui-with-sbcl
ANSI #commonLisp Improving my condition !
https://screwlisp.small-web.org/conditions/improving-my-condition/
I finally modify my condition handling per @kentpitman's notes on the Tuesday-night-in-the-Americas lispy gopher climate podcast last week (links in the article or currently pinned onto this mastodon).
The gist is to specify the condition the restart is being found for, since if more than one condition is signalled (error happens?) the different conditions will have different restart points.
#programming (non) #error handling
This week's project is a high-performance, RFC 4180 (CSV) compliant #commonlisp library: fast-csv.
My benchmarks show it is ~3.5x/1.5x (read/write) faster than fare-csv and ~20x/4.5x faster than cl-csv.
I measure about 2-7x speedup in comparison to numpy, with real-world files, on my machine.
fast-csv is also a streaming parser, which means it can process arbitrarily large files.
Available here: https://sr.ht/~hajovonta/fast-csv/
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst