Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site rtech.ARPA Path: utzoo!watmath!clyde!burl!ulysses!unc!mcnc!decvax!tektronix!hplabs!amdahl!rtech!markh From: markh@rtech.ARPA (Mark Hanner) Newsgroups: net.ai Subject: Re: Thus spake the DoD... Message-ID: <215@rtech.ARPA> Date: Wed, 6-Mar-85 22:44:14 EST Article-I.D.: rtech.215 Posted: Wed Mar 6 22:44:14 1985 Date-Received: Sat, 9-Mar-85 06:32:56 EST References: <313@wdl1.UUCP> Organization: Relational Technology, Berkeley CA Lines: 24 > ....there is a strong built-in assumption > in most LISP systems that the user wants all the programming tools available > at all times....the idea that one would want to run LISP > programs without everything in the standard system present was totally alien > to his way of thinking. this has to do with what many lisp programs end up doing. functions are built dynamically as lists in response to a non-deterministic human input for later execution. a lisp programmer would certainly like to assume that all of the functionality of his development system would be present at run time to be able to automate anything that might be done interactively. lisp is a different way of thinking than c (my home turf), as with apl, as with rpg2, as with quel, ad nauseum. use the proper tool for the task (no code generators in apl ;-)), but at least give us .o files that talk to each other... -- cheers, mark hanner (markh@rtech.ARPA) "there is a motorcycle in new mexico." -r.brautigan