If you use or tried running Medley Interlisp, what things did you discover later on that you wish you knew? We would appreciate your feedback.
#Lisp
16 posts13 participants1 post today
#oldComputerChallenge
https://screwlisp.small-web.org/occ/25/jul17.txt
In which I dig up my cryptic reference to rpg's ( #lisp )
The Structure of a Programming
Language
Revolution
's
reference to Teitelman's thesis on advice in the 60s, while already tired from writing my other article today.
#leonardoCalculus #Sandewall #programming #objectOriented #simulation #lisp #commonLisp
I feel like this article is one of those moments that is a monumental achievement for the writer themselves, but precedes adding glitzy picture making (which will eventually come too).
If you remember, I was recapitulating my somewhat failed #lispgamejam #gamedev . This time and in about half a week just now - I got the plant/insect/bird Breitenbergian Vehicle simulation workin'.
https://screwlisp.small-web.org/lispgames/LCKR-completing-the-simulation/
Nailed it!
I had some problems with positioning the cursor when there were empty new lines in the edited text. Without getting into gross details -- it works now! A bit of cleanup and optimization is underway, but I'm rather happy.
It is always nice to read a blog about dead programming languages, clearly aware of #lisp, but not dubbing it as dead itself.
https://www.hillelwayne.com/post/influential-dead-languages/
Hillel Wayne · 10 Most(ly dead) Influential Programming LanguagesThe other day I read 20 most significant programming languages in history, a “preposterous table I just made up.” He certainly got preposterous right: he lists Go as “most significant” but not ALGOL, Smalltalk, or ML. He also leaves off Pascal because it’s “mostly dead”. Preposterous! That defeats the whole point of what “significant in history” means.
So let’s talk about some “mostly dead” languages and why they matter so much.
#lispyGopherClimate w/ 500 hats of LambdaCalculus #HOPE_16 #PHREAKNIC previews #lisp #oldcomputerchallenge
https://communitymedia.video/videos/watch/8f0e5d5f-18d5-43c7-bfb2-4a866a59be0c
#hackThePlanet
#lispyGopherClimate #interview with 500 hats of @lambdacalculus
Their kofi: https://ko-fi.com/lambdacalculus
https://communitymedia.video/w/iEzEkc2SPuL5twaSnTEEq5 #archive
of #DOOM #redstaros #piratebox fame
Previewing their
#phreakNIC #technology #hacker
#HOPE #HOPE_16
talks!
Also #oldComputerChallenge happening RIGHT NOW https://screwlisp.small-web.org/occ/25/jul15.txt (I'm doing #xemacs emacs)
LambdaCalculus knows #emacs #lisp ...! And that's where it began then #commonLisp #CCL on the #macintosh
Learned about the existence of Rison today.
Merely looking at the syntax alone, this strongly suggests that Greenspun's Tenth Rule can be extended to JavaScript too. 
GitHubGitHub - Nanonid/rison: JavaScript/Python/etc RisonJavaScript/Python/etc Rison. Contribute to Nanonid/rison development by creating an account on GitHub.
Ghost Ops use the language of ghosts. Common Lisp for starters. #CommonLisp #Lisp #DeadSwitch
http://tomsitcafe.com/2025/07/14/the-silent-operators-language-common-lisp-basics/
Tom's IT Cafe · The Silent Operator’s Language – Common Lisp BasicsLanguages rise and fall.Syntactic sugar.Hair-raising formulas.One claims speed. Another elegance. Common Lisp stayed silent.Evolved in peace.Only a few were brave enough to touch it.Even fewer live…
Got the final chip emulator ported to SatouSynth from YunoSynth: the YM2413 (aka VRC7). So now the two libraries have the same chips implemented, one in #CommonLisp, one in #CrystalLang. SatouSynth (the #lisp one) is just slightly ahead in terms of functionality since I didn't back-port VGM seeking into YunoSynth yet, but I will soon, probably in a day or two.
This also means #benben is now much closer to a v0.7.0 release. Just gotta fix up some unimplemented command line arguments, then finish the milestone for v0.7.0 (just one item left), then just do a thorough round of testing.
Testing will be a bit longer this time since the whole program was rewritten from scratch in Common Lisp, so I want to make sure everything is just right. I'll of course post new development AppImages as I go.
So my guess? Benben v0.7.0 will be out this fall.
#LinuxAudio
#programming #formal #ontology #lisp #Sandewall #knowledgeRepresentation #article #leonardoCalculus
Leonardo Calculus Knowledge Representation: Fleshing out organism’s attributes
Adding attributes to the organism type (plant, insect and bird are all subsumed-by organism). I also add a coelacanth of type organism to a world entityfile. In my view, quite a good and informational/instructional article if I do say so. What do you think?
https://screwlisp.small-web.org/lispgames/LCKR-fleshing-out-organisms-attributes/
screwlisp.small-web.orgLeonardo Calculus Knowledge Representation: Fleshing out organism’s attributes
This toot was composed in #emacs using https://codeberg.org/emocoder/mastodon.el with the following #lisp
```
(require 'mastodon-toot)
(let* ((code (buffer-string))
(toot
(string-join
`("This toot was composed in #emacs using https://codeberg.org/emocoder/mastodon.el with the following #lisp\n"
"```"
,(format "%s\n" code)
"```\n") "\n")))
(mastodon-toot--compose-buffer nil nil nil toot))
```
Codeberg.orgmastodon.elEmacs client for Mastodon
#article #ontology #programming #formal #lisp #concrete
https://screwlisp.small-web.org/lispgames/plant-insect-bird-ontology/
Plant Insect Bird practical formal ontology with Leonardo calculus
I revisit my #lispgames #gamejam #gamedev. In this article I create a formal ontology to be a vehicle for my concrete game redux of the jam (which had been lacklustre if technically interesting. Let's be technically interesting and have more lustre this time round.
Thoughts, commentary, ontological guidance gentle and stern if you will please.
From Joe Marshall's blog on Planet Lisp:
'Go programs make a lot more sense if you pronounce `if err != nil` as "inshallah".'
funcall.blogspot.comAn observationA blog about computers, functional languages, Lisp, and Scheme.
Replied in thread
@robpike Cool to look at, but it's a well-known first-order error term of Stirling’s formula revealing itself in base-10 notation.
My code here differs slightly from what you did to get your results, but look at the (stubborn( similarities.
(defparameter *bernoulli-coeffs*
'(-1/12 1/360 -1/1260 1/1680 -1/1188)) ; not working this out from scratch lol
(defun log-error (n &optional (terms 3))
(let ((sum 0d0) (nk n))
(dotimes (j terms)
(setf sum (+ sum (/ (float (nth j *bernoulli-coeffs*) 1d0) nk)))
(setf nk (* nk n n))) ; N, N³, N⁵, …
sum))
(defun stirling-ratio (k &optional (places 25) (terms 3))
(let* ((n (expt 10d0 k))
(ratio (exp (log-error n terms))))
(format nil "~,vF" places ratio)))
(defun show-pattern (&optional (max-k 6) (places 25) (terms 3))
(loop for k from 1 to max-k
do (format t "k = ~d ⇒ ~a~%" k
(stirling-ratio k places terms))))
Try this with (show-pattern 15 17). This is from clisp, but it should work on any common lisp.
There are people much smarter than I that can probably do this more efficiently. but this should show you why you see what you see.
Google "borrow trail" for more info about what it is.
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
Lisp journey · Lisp error handling (advanced): how handler-bind doesn't unwind the stack - Lisp journey
The TEdit WYSIWYG editor of Medley Interlisp has a split window mode that shows different parts of a document. To split at the cursor or unsplit, middle-click on the title bar and select Split Window or Unsplit Window.