3 ms·
Reminds me of a line from the Common Lisp Cookbook[1]: > Keep in mind that it was written at a time where Lisp Machines were at their peak. On these boxes Lisp
by djha-skin 3y ago
Reminds me of a line from the Common Lisp Cookbook[1]:
> Keep in mind that it was written at a time where Lisp Machines were at their peak. On these boxes Lisp was your operating system!
Common Lisp OS interfacing is not part of the standard, because there were no "operating systems" back when Common Lisp Standard started out other than Lisp itself. It, too, was a casualty of the OS wars, but it lives on in user space, where it now lurks, and bides its time.
1: https://lispcookbook.github.io/cl-cookbook/os.html https://lispcookbook.github.io/cl-cookbook/os.html
- gumby 3y ago> there were no "operating systems" back when Common Lisp Standard started out other than Lisp itself. This isn't really true, of course. Sure, Commonlisp was mainly the standardization of MIT Lipsm lisp (based on MACLISP), influenced by good ideas from PARC's D-Machine Interlisp-D (based on Interlisp). Both ran on the bare iron of their respective machines. But their predecessors MACLISP and BBN Interlisp both ran on PDP-10s under Tenex, Twenex (and those latter two's official OSes) and MACLISP also on PDP-10 ITS (its original home) Multics (both hardware and an OS). Other MACLISP-ish Lisps such as VAXLISP (VMS) and franz lisp (Unix on PDP-11s and Vaxes) contributed as well. These were all user space environments.
- gumby 3y agoBy the way the PDP-6 (and thus its dependent the PDP-10) was explicitly designed to be a "Lisp machine" -- a machine word was a cons and many fundamental lisp operations like car and cdr were single machine instructions.