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

@screwlisp

You can pick up the document 'Signalling and Handling Conditions' from this index page:

http://nhplace.com/kent/ZL/

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

#lisp Kent M Pitman visual demo of 1984 #lispm Cross Referenced Editing Facility program for OpenUniversity #programming

https://toobnix.org/w/jWdWsrBLCFkFQYrfzbzCR8

#lispyGopherClimate Sunday morning in Europe with #lisp # live @kentpitman

Going over proto #emacs, #cref, #lispm #computerScience #softwareEngineering #GUI history ! Ask questions in #lisp on #irc now please !

https://toobnix.org/w/gXLXQqxf5MYg1NDF2Ua6oA 15 minutes to live.

#Archive: https://toobnix.org/w/jWdWsrBLCFkFQYrfzbzCR8

https://communitymedia.video/w/h1jdbHm8xTj5VEDuCWAbBW
#lispyGopherClimate #technology #podcast #weekly

featuring @kentpitman @ramin_hal9001 @jns
Longterm #reliability , the #climateCrisis , technology and knowledge

Kent has found the source to his Cross referenced editing facility from Open University #lisp #lispm example.

#scifi #books with this theme? Ending of Cats Cradle?

On the #art side check, @prahou 's #unix_surrealism, https://photronic.art

Happy #lambdaMOO year! 35 years! https://lambda.moo.mud.org as always.

Current work in #LispMachine world is to implement the bus interface for the CADR 4 project (https://github.com/ams/cadr4).

That is so we can add a spy interface .. #LispM #MIT #LM-3