#zetalisp — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #zetalisp, aggregated by home.social.
-
As part of my history project, I was looking for a document I wrote that offered specific advice on converting Maclisp and Zetalisp to Common Lisp.
I had to laugh when I found it. It's already published as part of the Sunday Morning Edition of the Pitmanual (the webbed version of the Revised Maclisp Manual, the printed version of which was the Saturday Evening Edition).
The printed version does not contain the conversion guide. It was an "extra" I through in as part of the webbing. But it's perhaps hard to find, so I thought I'd say it out loud. It's several pages that begin here:
https://maclisp.info/pitmanual/cl-conv-01-intr.html
#Lisp #Maclisp #Zetalisp #CommonLisp #KentsHistoryProject #Lisp #ComputerHistory
-
I couldn't find a copy of the memo named "Loop Iteration Macro" by Glenn Burke and David Moon, January 1981 (MIT/LCS/TM-169) at MIT's dSpace site, or anywhere else. So I scanned in my copy and have uploaded it to my web site.
NOTE WELL: This document was written prior to CLTL and describes a facility that was available in MACLISP and the Lisp Machine's Zetalisp. Common Lisp drew design ideas from this, but the syntax, semantics, and associated functions/macros described in this are NOT the same as what Common Lisp offers.
For example, my recollection from long ago (which I did not re-check before making this post) is that there are other differences in syntax because this earlier version of Loop was underconstrained in the ordering of the keywords in a way that let you write some expressions that the committee felt might confuse people with their results.
But also, for reasons that slip my mind, Common Lisp did not adopt the define-loop-path macro that is described starting on page 19.
http://nhplace.com/kent/History/maclisp/MIT-LCS-TM-169-Loop-Iteration-Macro.pdf
#lisp #maclisp #loop #iteration #ComputerHistory #KentsHistoryProject #lisp #LispM #Zetalisp #CommonLisp
cc @screwlisp
-
P.S.
Nice fractal!
The index is a good read:
...
circular-link 60
...
no-file-system 56
...
singular-matrix 48
...#Conditions
#ConditionSystem
#ErrorDetection
#ErrorSignalling
#Lisp
#ZetaLisp -
P.S.
Nice fractal!
The index is a good read:
...
circular-link 60
...
no-file-system 56
...
singular-matrix 48
...#Conditions
#ConditionSystem
#ErrorDetection
#ErrorSignalling
#Lisp
#ZetaLisp -
P.S.
Nice fractal!
The index is a good read:
...
circular-link 60
...
no-file-system 56
...
singular-matrix 48
...#Conditions
#ConditionSystem
#ErrorDetection
#ErrorSignalling
#Lisp
#ZetaLisp -
P.S.
Nice fractal!
The index is a good read:
...
circular-link 60
...
no-file-system 56
...
singular-matrix 48
...#Conditions
#ConditionSystem
#ErrorDetection
#ErrorSignalling
#Lisp
#ZetaLisp -
P.S.
Nice fractal!
The index is a good read:
...
circular-link 60
...
no-file-system 56
...
singular-matrix 48
...#Conditions
#ConditionSystem
#ErrorDetection
#ErrorSignalling
#Lisp
#ZetaLisp -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
#OldComputerChallenge #finalTransmission
#gopher
gopher://tilde.club/0/~screwtape/2023-17th-July-1-still-16th-in-some-TZ-lisp-docs.txt
gopher://tilde.club/0/~screwtape/2023-17th-July-2-final-transmission.txt
gopher://tilde.club/1/~screwtape/
It's now 000UTC 17th - 30 minutes.
back to
gopher://gopher.club/1/users/screwtape/
gopher://tilde.institute/1/~screwtape/
https://archives.aNONradio.net/#screwtapeNext up, @nutilius ' #TwoHoursLispPerDay challenge !
#interlisp #zetalisp #EmbeddableCommonLisp #MCCLIM for me !
(That's + two hours, I'm not cutting down ;p) -
#OldComputerChallenge #finalTransmission
#gopher
gopher://tilde.club/0/~screwtape/2023-17th-July-1-still-16th-in-some-TZ-lisp-docs.txt
gopher://tilde.club/0/~screwtape/2023-17th-July-2-final-transmission.txt
gopher://tilde.club/1/~screwtape/
It's now 000UTC 17th - 30 minutes.
back to
gopher://gopher.club/1/users/screwtape/
gopher://tilde.institute/1/~screwtape/
https://archives.aNONradio.net/#screwtapeNext up, @nutilius ' #TwoHoursLispPerDay challenge !
#interlisp #zetalisp #EmbeddableCommonLisp #MCCLIM for me !
(That's + two hours, I'm not cutting down ;p) -
#OldComputerChallenge #finalTransmission
#gopher
gopher://tilde.club/0/~screwtape/2023-17th-July-1-still-16th-in-some-TZ-lisp-docs.txt
gopher://tilde.club/0/~screwtape/2023-17th-July-2-final-transmission.txt
gopher://tilde.club/1/~screwtape/
It's now 000UTC 17th - 30 minutes.
back to
gopher://gopher.club/1/users/screwtape/
gopher://tilde.institute/1/~screwtape/
https://archives.aNONradio.net/#screwtapeNext up, @nutilius ' #TwoHoursLispPerDay challenge !
#interlisp #zetalisp #EmbeddableCommonLisp #MCCLIM for me !
(That's + two hours, I'm not cutting down ;p) -
#OldComputerChallenge #finalTransmission
#gopher
gopher://tilde.club/0/~screwtape/2023-17th-July-1-still-16th-in-some-TZ-lisp-docs.txt
gopher://tilde.club/0/~screwtape/2023-17th-July-2-final-transmission.txt
gopher://tilde.club/1/~screwtape/
It's now 000UTC 17th - 30 minutes.
back to
gopher://gopher.club/1/users/screwtape/
gopher://tilde.institute/1/~screwtape/
https://archives.aNONradio.net/#screwtapeNext up, @nutilius ' #TwoHoursLispPerDay challenge !
#interlisp #zetalisp #EmbeddableCommonLisp #MCCLIM for me !
(That's + two hours, I'm not cutting down ;p) -
@trurl
I was thinking of asking for that. I am also especially interested in elisp / major mode design at the moment because for old computer challenge I have been using the #lispm whose emacs implementation is #zmacs with #zetalisp major modes (and not gnu or lucient emacs with emacs-lisp).I wonder if there is or was a near-antecedent to planner-mode major mode for Zmacs ? @amszmidt are you familiar with any TODO style major modes now or previously for zmacs?
-
The #Telegram and #Matrix groups named #FamilyOfLisp are now synchronized (bridged):
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt
The two groups are for friendly exchange and dialogue on topics related to the Family of #Lisp #programming languages.
🌺
🏷️ #Scheme #CommonLisp #Racket #Clojure #DylanLang #ELSConf #AMOP #CLOS #InterLisp #OpenGenera #LispMachine #Medley #ConnectionMachine #Symbolics #AutoLisp #MacLisp #ZetaLisp #EuLisp #ISLisp #CLHS #SICP #AIMA #CLtL2 #PAIP #HTDP
-
The #Telegram and #Matrix groups named #FamilyOfLisp are now synchronized (bridged):
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt
The two groups are for friendly exchange and dialogue on topics related to the Family of #Lisp #programming languages.
🌺
🏷️ #Scheme #CommonLisp #Racket #Clojure #DylanLang #ELSConf #AMOP #CLOS #InterLisp #OpenGenera #LispMachine #Medley #ConnectionMachine #Symbolics #AutoLisp #MacLisp #ZetaLisp #EuLisp #ISLisp #CLHS #SICP #AIMA #CLtL2 #PAIP #HTDP
-
The #Telegram and #Matrix groups named #FamilyOfLisp are now synchronized (bridged):
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt
The two groups are for friendly exchange and dialogue on topics related to the Family of #Lisp #programming languages.
🌺
🏷️ #Scheme #CommonLisp #Racket #Clojure #DylanLang #ELSConf #AMOP #CLOS #InterLisp #OpenGenera #LispMachine #Medley #ConnectionMachine #Symbolics #AutoLisp #MacLisp #ZetaLisp #EuLisp #ISLisp #CLHS #SICP #AIMA #CLtL2 #PAIP #HTDP
-
If you would like to come over to a friendly group on Telegram focused on the programming languages in the #FamilyOfLisp — please feel welcomed to join!
We are here:
🌺
🏷️ #Lisp #Scheme #CommonLisp #Racket #InterLisp #Clojure #BaLindaLisp #Hy #ELSConf #ZetaLisp #LispMachine #ConnectionMachine #ThinkingMachines #Emacs #AutoLisp #CLOS #AMOP #SICP #CLtL2 #PAIP #AIMA #PCL #Symbolics #Genera #DylanLang #LFE #ISLisp #Arc #Janet #Jank #OnLisp #HTDP #CLHS #EuLisp