#lisp

aELARAJI (skinshafi)aelaraji@pl.aelaraji.com
2026-01-26

I don't know why but watching @cwebber 's Unlock Lisp / Scheme's magic: beginner to Scheme-in-Scheme in one hour kind of cured my parentheses induced anxiety 🥳

#scheme #lisp

The Natural Escapement

lemmy.ca/post/59307908

Daniel Kochmańskijackdaniel@functional.cafe
2026-01-26

I wrote a thing, I wrote a thing!

turtleware.eu/posts/McCLIM-and

This tutorial will be included in McCLIM manual (and other parts too).

#mcclim #lisp

2026-01-26

Just a reminder that meta.lisp.community is a new Lisp discussion forum about various classic and modern dialects. A community-run asynchronous discussion board is a great resource for those who prefer forums over chat or proprietary platforms.

community.metalisp.dev

#lisp #CommonLisp #forum

2026-01-26

#lisp + #haskell enthusiasts who happen to write/try #coalton, do you write .coal files or .lisp?
I've been trying #coalton for last few weeks and am using .lisp, but given that I always only have a single in-readtable call per file, I am thinking it only make sense to not have to do coalton-toplevel all the time. I create a new coalton-toplevel for a new "block" (where block = whatever make sense to me) so I can keep my lisp workflow without having to re-eval everything.

2026-01-26

sysp: Systems Lisp compiling to C with homoiconic macros, refcounted memory, Hindley-Milner type inference

fed.brid.gy/r/https://github.c

2026-01-26

New Common Lisp Cookbook PDF (Typst quality)

sopuli.xyz/post/40165498

Lobsterslobsters
2026-01-26

sysp: Systems Lisp compiling to C with homoiconic macros, refcounted memory, Hindley-Milner type inference lobste.rs/s/d4y8rq
github.com/karans4/sysp

The Medley Interlisp Projectinterlisp@fosstodon.org
2026-01-25

RE: fosstodon.org/@interlisp/11592

Our 2025 annual report presents the work we did last year to revive the Medley Interlisp system and bring its ecosystem to the 21st century. We would appreciate it if you could share the report, which may be of interest to potential users and other software preservation projects.

#interlisp #lisp #retrocomputing

So not only does the Apple LiSA consider you a DOLT but so does the symbolics lisp machine, but with serifs #vintagecomputing #apple #lisp #retrocomputing

icm.museum

Lobsterslobsters
2026-01-24

vivace-graph-v3: CL graph database & Prolog implementation lobste.rs/s/mstij5
github.com/kraison/vivace-grap

2026-01-24

lispE: Lisp interpreter with Data Structure, Pattern Programming, High level Functions, Lazy Evaluation

fed.brid.gy/r/https://github.c

Lobsterslobsters
2026-01-24

lispE: Lisp interpreter with Data Structure, Pattern Programming, High level Functions, Lazy Evaluation lobste.rs/s/mcaxcn
github.com/naver/lispe

2026-01-23

I was curious about how long I've been an Emacs user and through some online digging I found an absolutely ancient screenshot. This was me learning how to program back in 2015. Here I was, using Emacs and going through my first ever programming book. So cute.

#emacs #lisp

Screenshot showing two windows in the i3 window manager. On the left is a window with a PDF displaying "Common Lisp: A gentle introduction to symbolic computation". On the right is a window showing a terminal, rxvt, with Emacs running a SLIME REPL sessions with lots of little boolean lisp forms.
2026-01-23

Old paper:
John Launchbury and Simon L Peyton Jones. 1995. *State in Haskell*
sci-hub.st/10.1007/BF01018827

What interests me more is that the journal used to called *LISP and Symbolic Computation*, the intersection of the two topics that I am most interested.

Later the the “LISP” in the journal name was changed to “Higher-Order” in 1998, after which the famous #R5RS
was published on it.

#Haskell #LISP #Scheme #SymbolicComputation

State in Haskell 
JOHN LAUNCHBURY 
Oregon Graduate Institute, PO Box 91000, Portland, OR 97291-1000
jl@cse.ogi.edu
SIMON L PEYTON JONES 
University of Glasgow, G12 8QQ, Scotland
simonpj@dcs.glasgow.ac.uk

Abstract

Some algorithms make critical internal use of updatable state, even though their external specification is purely functional. Based on earlier work on monads, we present a way of securely encapsulating stateful computations that manipulate multiple, named, mutable objects, in the context of a non-strict, purely-functional language. The security of the encapsulation is assured by the type system, using parametricity. The same framework is also used to handle input/output operations (state changes on the external world) and calls to C.Summary of the paper: 
We have described a small collection of: 
• Primitive state transformers, namely returnST, newVar, readVar, and writeVar; 
• "Plumbing" combinators, which compose state transformers together, namely thenST and its derivatives, thenST_, listST, mapST, and so on. 
• An encapsulator, runST, which runs a state transformer on the empty state, discards the resulting state, and returns the result delivered by the state transformer.A cover image of the journal LISP and Symbolic Computation, 1991-01: Vol 4
2026-01-23

Short notice streaming today at 12pm EST / 18:00 UTC. Working on and things today related to FBO management

twitch.tv/endparen

2026-01-23

tried simple parsing algorithm, Shunting yard algorithm invented by Dijkstra, in common lisp

tilde.club/~aerphanas/03B08.ht

#commonlisp #lisp

emacs running sly in package cl-user with history, (transform 70 '* 6 '+ 10 '- 10) evaluate to (- (+ (* 70 6) 10) 10), (eval (transform 70 '* 6 '+ 10 '- 10)) to 420 (9 bits, #x1A4)

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst