From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!cmcl2!rutgers!ucla-cs!zen!ucbvax!VLSI.JPL.NASA.GOV!larry
From: larry@VLSI.JPL.NASA.GOV
Newsgroups: comp.lang.ada
Subject: Adathink
Message-ID: <870806210856.08p@VLSI.JPL.NASA.GOV>
Date: Fri, 7-Aug-87 00:08:55 EDT
Article-I.D.: VLSI.870806210856.08p
Posted: Fri Aug  7 00:08:55 1987
Date-Received: Sat, 8-Aug-87 15:19:59 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

As for as self-modifying code is concerned, I think those who've 
done "AI-type" products find that very little code of this sort 
is needed or desirable.  This is one reason why compilable LisP 
is such a useful tool.  Self-referencing can also be done in 
other ways than self-modifying code.

The relation between AI languages and Ada/C/etc. seems to be that 
LisP/Smalltalk/etc. are very effective for exploratory pro-
gramming and prototyping, but when a system is to be delivered 
it's best to translate it to a compiled language first.

As for control structures, this is a subject I'd like to see some 
advice on too.  I'm writing an EMACS like text-processor and I'll 
admit that I'm having problems with the over-all architecture.  
(Maybe because I've been immersed for the past few months in C 
code for several EMACSes and my perceptions have been corrupted!)

              Larry @ jpl-vlsi