"Lisp needs more…": the rant of a rant, some perspective, a call to action. WDYT? https://dev.to/vindarel/common-lisp-needs-more-documentation-tools-and-ideas-where-are-we-on-this-io sometimes it bears repeating.
"Lisp needs more…": the rant of a rant, some perspective, a call to action. WDYT? https://dev.to/vindarel/common-lisp-needs-more-documentation-tools-and-ideas-where-are-we-on-this-io sometimes it bears repeating.
Kent Pitman, Scott Zimmermann, Ramin Hal, screwlisp #lisp conditions, #python, Wolfram #lispyGopherClimate
#LispyGopherClimate #live 0UTC https://communitymedia.video/w/tF2sa14dgMasWzGt1PryDb
@kentpitman 's #commonLisp industry condition system for #python finally upped. #video https://gamerplus.org/@screwlisp/115731324866343200 <- if you #retoot one 2025 #peertube about #typeChecking half programs' local restarts, make it this one <3 <3 <3 #programming
sczm from #emacsconf #slime #python #maybe viz Kent's presentation
My 2026 theme is sharing knowledgebases on #itchio. #gamedev now that my #LeonardoCalculus #emacs just works. https://lispy-gopher-show.itch.io/leonardo-calculus
Just the moment I find out one can do reliable list-of-X types on most #CommonLisp implementations, I learn that the library that'd have most benefited from this knowledge, trivial-types (https://github.com/m2ym/trivial-types), has been archived since 2018. God why, I want to bring cool stuff to people, but I don't want to fork the ecosystem 😰
https://communitymedia.video/w/c2D8hXG2zixrjz6jyX96N9
#python #commonLisp #softwareEngineering #programming
Lisp industry adopted modern condition handling adapted to python introduced by @kentpitman .
An incredibly important realisation of dynamic #typeTheory with modern industry adoption. (Except conditions are more general than type checking and errors). See the peertube description for a longer spiel I will not reproduce here.
45 minute video, I snipped the after-discussion from the livestream.
@chemoelectric I don't think this is true, or I don't understand what you mean. A lambda form for example will return a function as a value, and you can bind it to a variable or do some other stuff with it. Also the #'f syntax (same as (function f)) returns the function associated to the symbol f, as a value.
In CL (with MOP at least, which is not technically in the ANSI standard I think) you can do something similar by defining classes with the metaclass "funcallable-standard-class", which makes it a class that's also a function, which is pretty cool IMO.
Hiding stuff is usually not a good approach IMO, you probably shouldn't put potentially dangerous stuff right in front of people so they trip over it (makes me think of C or C++ for example), but for people who know what they're doing it should be easily accessible and well documented.
I was sick yesterday sorry, and today to get back in the rhythm redid my holistic README post- my- own- #emacsconf for my #LeonardoCalculus #softwareIndividuals
https://codeberg.org/tfw/pawn-75
In which I have an agent periodically send a stylized date to its host individuals' host emacs' minibuffer.
I aim to transcribe and public -ify up the first part of the Pitman Errors video before the show today. #lisp #commonLisp #emacs
Finally got myself to publish the long-in-the-making post on how I manage #CommonLisp project dependencies. Been leaking through all the communication lately, so some of you know that I use submodules btw and they do work for my smart #REPL s and testing setups. Find details in “Common Lisp Dependency Vendoring with Submodules:”
RE: https://framapiaf.org/@vindarel/115724692300110690
This is *great*. 🤩 Glad to see furious development happening over at Lem-land. #lisp #lem #commonlisp #editor
Lem editor news: Living Canvas.
> a visual code analysis feature that displays function call graphs as an interactive, Figma-like canvas. It helps developers understand code structure, relationships, and execution flow.
@arclight @millie and for the rest, especially high magic stuff, you have #CommonLisp
so roswell uses the quicklisp dist by default, right?
https://github.com/atgreen/icl is installable via roswell, but fails because a dependency, cl-version-string is not in the default dist (it is on ultralisp).
I just completed "Playground" - Day 8 - Advent of Code 2025 with Common Lisp!
Not the most efficient at 16 seconds for part 2, but it gets it done.
https://adventofcode.com/2025/day/8
https://github.com/argentcorvid/aoc-2025/blob/main/2025d8.lisp
T minus 15 minutes. I'm watching #lisp and #emacsconf on #irc . #live #interview #softwareEngineering #commonLisp #errorHandling https://toobnix.org/w/gXLXQqxf5MYg1NDF2Ua6oA
@kentpitman
Questions about Kent's port of ANSI cl's condition handling to #python #commonLisp (T- 40 minutes)
-Who is the target audience? Lisp or python users?
-Does it offer new functionality or just [] expressivity?
-How does it integrate with python's native conditions?
-Why not integrate in a lower level way?
-How was adoption of this condition system achieved in Common Lisp?
-Where would this be useful?
-Are there ways people can get involved?
@kentpitman
[] at 8am 0UTC=9am CET, ( #commonLisp 's) @kentpitman is going to give a live video #demo of his lisp-style error handling in #python . At this #peertube #live link:
Archive will be up here tomorrow!
We also expect to talk about the #slime swanky python #emacsconf talk: https://emacsconf.org/2025/talks/swanky/ whose author should be on the Tuesday-night-in-the-Americas show this week.
If you have #mastoQuestions please leave them here #AMA (on topic), and I guess #lisp on #irc live. #programming
https://screwlisp.small-web.org/fundamental/errors-in-ansi-common-lisp/
#errorHandling in #commonLisp vs common #agile (I look forward to your ripostes) #checkType #softwareEngineering #debugging
I hope I demoed a usable example of lisp's binding error handlers, which I think are a common point of confusion because it is a #lisp principle that is still just secret alien technology. I also point you to and describe finding lisp's included demos
Until eight hours from now, when https://en.wikipedia.org/wiki/Kent_Pitman demos his python port of it live.
#maxima #commonLisp #CAS #algebra #article https://screwlisp.small-web.org/fundamental/common-lisp-maxima-finally/
> (integrate '(tan x) 'x 0 1)
(* -1 (LOG (COS 1)))
> '(1 2 3 4)
(1 2 3 4)
> (coerce * '(SIMPLE-ARRAY (COMPLEX DOUBLE-FLOAT) (*)))
#(#C(1.0 0.0) #C(2.0 0.0) #C(3.0 0.0) #C(4.0 0.0))
> (maxima-fft:fft-r2-nn *)
#(#C(2.5 0.0) #C(-0.5 -0.5) #C(-0.5 0.0) #C(-0.5 0.5))
I guess #retrocomputing but current was August, so.
Also have a note about Kent demoing his implementation of his-ansi-cl style error handling introduced to python.
I'll stream #McCLIM #OpenGL and #CommonLisp things today, 12/12, at 12pm CST/ 18:00 UTC
I didn't think I'd have time today due to IRL things but I suddenly have some time. We'll start by cleaning up / archiving a failed index buffer attempt and then will find the next issue that needs tackling.