Lisping like it's the 1970s: my setup and initial experience with Interlisp-10, the Interlisp implementation for the PDP-10.
https://journal.paoloamoroso.com/paoloamoroso/exploring-interlisp-10-and-twenex
Implementing interactive test filtering:
https://youtu.be/8hqA_iSP3h4
Over the next few weeks (or more) I want to spend some time with a #Lisp language. I'm now in a kind of embarrassment of riches situation.
I could get deeper into #Clojure which I'm already quite fluent with (e.g. get into macros, understand transducers, core.async.flow).
I could finally learn #CommonLisp. Tried it a few years ago, liked it, never did anything with it.
Or I could dive into #scheme other than #Racket (#Guile, #Gambit, #Gerbil, #ChezScheme), see what's cooking there.
I came across a nice blog I didn't know, Lispology, by the developer of uLisp. He mostly focuses on Common Lisp and writes short, clear posts with readable code about interesting problems and projects, often with elegant solutions and the recurring theme of recursion. The blog offers a lot of tidbits and insights into using Lisp.
Is there a #mastodon instance (or any other kind of thing interoperable with the #fediverse) that supports editing links between elements of a thread so you can fix errors in sequencing? If so I would happily migrate and help fund! #lisp #c #microblogging
Is there a #mastodon instance that supports editing links between elements of a thread so you can fix errors in sequencing? If so I would happily migrate and help fund! #lisp #c #microblogging
Indeed, and very much so.
The evolution and history of Lisp thinking,
including the speed of this evolution,
is very instructive and very interesting.
Another case study:
the road to lexical binding, lexical closures, and lexical scope.
One of many relevant papers has a memorable title,
"The Function of FUNCTION in Lisp".
@masso
If you look at Allen's Anatomy of Lisp, in the late 70s he's still teaching with M-expressions as the mathematical language, and S-expressions as the computer logic realizing those M-expressions.
However if you look at Pratt's paper on Pratt parsers around 1970, there is the remark that a great breadth of lisp programmers prefered writing and reading lisp's S-expressions rather than looking at the -onto M-expressions they implement.
Lisp from Nothing, Second Edition
@vnikolov @m3tti @lisp If you want to actually program in M-Exprs, try Beowulf. I implemented a REPL that could read M-Exprs and well as S-Exprs simply to see how ergonomic they would be to code in, but I didn't find that, for me, they offered any advantage. Still, it's interesting to be able to do it.
The idea of Beowulf was that it should be as nearly as possible a functional reimplementation of #Lisp 1.5, with the same semantics.
Well, there *were* problems in my trigonometry functions. But I spent a lot of time hunting bugs in them that weren't there. It turns out the real bug was in my tree algorithm: I wasn't backtracking correctly.
However, this now works, and you may play with it if you wish.
Lisp from Nothing, second edition is out
HN thread, with the author, that discusses the book, but also other interesting libraries, language implementations as well as related books
Retrocomputing - MIT CADR Lisp Machines
Retrocomputing - MIT CADR Lisp Machines
