Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!gatech!mcnc!godot!thorn
From: thorn@godot.radonc.unc.edu (Jesse Thorn)
Newsgroups: comp.lang.lisp
Subject: Re: What is needed (was: Tired C programmer)
Summary: Lisp delivery environments
Message-ID: <1026@godot.radonc.unc.edu>
Date: 5 May 89 16:06:05 GMT
References: <1989Apr30.183925.19847@cs.rochester.edu> <89May5.070055edt.39756@neat.ai.toronto.edu>
Distribution: na
Organization: Radiation Oncology NCMH/UNC, Chapel Hill, NC
Lines: 22

In article <89May5.070055edt.39756@neat.ai.toronto.edu> rayan@AI.TORONTO.EDU (Rayan Zachariassen) writes:
>
>Indeed, but that is only half the problem.  The other half is the software
>equivalent of a "Delivery Vehicle" environment, namely some way of providing
>Lisp applications that doesn't require a 5 megabyte binary to do a /bin/cat
>equivalent.  

You really need some way of excluding development code from delivery
code especially if you are doing commercial product development.
It is really embarrassing to tell the client that half of the memory
they need to buy for their machines is to support the compiler and editor.

I believe that VAXLisp under VMS allows you to build "delivery"
worlds sans development tools. 

Any others?

Jesse Thorn
Radiation Oncology
UNC Hospitals at Chapel Hill
Chapel Hill, NC 27516
thorn@godot.radonc.unc.edu