Nil | |
Paradigms: | Multiparadigm |
Family: | Lisp |
Designer: | Jon L White |
Developers: | Jon L White, Guy L. Steele Jr., Richard P. Gabriel |
Typing: | dynamic, strong |
Programming Language: | VAX assembly |
Discontinued: | Yes |
Platform: | VAX |
Operating System: | VAX/VMS |
File Formats: | --> |
Influenced By: | Lisp, Maclisp |
Influenced: | Common Lisp, T |
New Implementation of LISP (NIL) is a programming language, a dialect of the language Lisp, developed at the Massachusetts Institute of Technology (MIT) during the 1970s, and intended to be the successor to the language Maclisp.[1] It is a 32-bit implementation,[2] and was in part a response to Digital Equipment Corporation's (DEC) VAX computer. The project was headed by Jon L White,[3] with a stated goal of maintaining compatibility with MacLisp while fixing many of its problems.
The Lisp language was invented in 1958 by John McCarthy while he was at Massachusetts Institute of Technology (MIT).[4] From its inception, Lisp was closely connected with the artificial intelligence (AI) research community, especially on PDP-10 systems. The 36-bit word size of the PDP-6 and PDP-10 was influenced by the usefulness of having two Lisp 18-bit pointers in one word: "The PDP-6 project started in early 1963, as a 24-bit machine. It grew to 36 bits for LISP, a design goal."[5] Lisp was used as the implementation of the programming language Micro Planner that was the foundation for the famous AI system SHRDLU. Lisp, in particular Maclisp (so named because it originated at MIT's project MAC) was also used to implement the Macsyma computer algebra system. In the 1970s, as AI research spawned commercial offshoots, the performance of extant Lisp systems became a growing problem.
Partly because of garbage collection (Lisp would use stop-and-copy garbage collection of its single heap for memory allocation[2]) and partly because of its representation of internal structures, Lisp became difficult to run on the memory-limited stock computer hardware of the day. This led to creating Lisp machines: dedicated hardware for running Lisp environments and programs. An alternative was to use the more powerful commodity hardware which was becoming available, especially the Digital Equipment Corporation (DEC) VAX.
NIL was an implementation of Lisp developed at MIT in the mid to late 1970s, and intended to be a modern successor to Maclisp that was able to run on stock hardware,[1] in contrast to Lisp Machine Lisp for the Lisp machines.[2] "Originally designed as the first modern Lisp dialect on stock hardware after the development of Lisp machine Lisp at MIT, it went on to become one of the main influences on the design of Common Lisp." (pg 63/294 of [2]) Since the users of the Macsyma program represented a large potential user base for NIL, it was necessary that NIL would be a large, complex system, and that speed would be imperative. For example, high-speed bignums was a requirement to support Macsyma, since NIL would be a failure with slow bignums.[6] Consequently, NIL ended up with a large base of VAX assembly language. These requirements led to a very aggressive and complex optimization strategy which was applied prematurely, with negative results on the final system.[7]
Concurrent with the effort to write NIL, a research group at Stanford University and Lawrence Livermore National Laboratory headed by Richard P. Gabriel were investigating the design of a Lisp to run on the S-1 Mark IIA supercomputer, S-1 Lisp. That Lisp was never fully functional, but was a test bed for implementing advanced compiler methods in a Lisp. Eventually the S-1 and NIL groups began collaborating.
Although unsuccessful in meeting its goals as a used language, NIL was important in several ways. First, it brought together Jon L. White, Guy L. Steele Jr., and Richard P. Gabriel, who were later to define Common Lisp.[1] Second, Jonathan Rees worked on part of the NIL project during a year away from Yale University. On returning to Yale, he was hired by the computer science department to write a new Lisp, which became the optimizing, native code Scheme system named T. In part, NIL begat this name, since "T is not NIL".[7]