At the time the Connection Machine was being designed and built, the only language being actively developed for it was an assembly-level language named PARIS. It became evident that a better way to program the machine was needed, and quickly. Waiting for the completion of Connection Machine Lisp was not an option. CM Lisp had been proposed by Danny Hillis, and development was expected to continue for several more years.
Development
A *Lisp interpreter was initially developed. It became apparent quickly that a *Lisp compiler, translating *Lisp into Lisp and PARIS, would be needed to attain the gigaFLOPS speed that was attainable in theory by a Connection Machine. The *Lisp compiler was written by Jeff Mincy and was first released in 1986. An application achieving more than two gigaFLOPS, a helicopter wake simulator, was developed by Alan Egolf, then an employee of United Technologies, and J. P. Massar, a Thinking Machines employee, in 1987. A *Lisp Simulator, an emulator meant to run *Lisp code on standard, non-parallel machines, was developed at the same time by J. P. Massar. This simulator still exists, and was ported to American National Standards InstituteCommon Lispin 2001. An older version written in the original CL, exists in the Carnegie Mellon Universityartificial intelligence repository. Later versions of *Lisp, involving significant upgrades to its functions and performance, were worked on by Cliff Lasser, Jeff Mincy, and J. P. Massar through 1989. *Lisp was implemented on the Thinking Machines CM5 circa 1990–1991 by J. P. Massar and Mario Bourgoin.
Implementation
StarLisp was written on Common Lisp, and thus had the full power of CL behind it. To use a Connection Machine, one needed a host or front-end. To use *Lisp, that front-end had to run CL. Symbolics' machines using Genera and Sun Microsystems workstations running Lucid Inc.'s Lucid Common Lisp were both used to operate *Lisp. StarLisp operated on Parallel Variables. These represented Connection Machine memory, and were essentially vectors: one element per CM processor. StarLisp consisted of standard operations on PVARS, like vector addition and multiplication, along with communication primitives that essentially reordered the elements of a PVAR using the CM's communication hardware to optimally route the data.
