Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!edcastle!aipdc
From: aipdc@castle.ed.ac.uk (Paul Crowley)
Newsgroups: comp.lang.misc
Subject: Re: A comment on language wars.
Message-ID: <9053@castle.ed.ac.uk>
Date: 11 Mar 91 00:35:47 GMT
References: <MARKF.91Mar6122504@montreux.ai.mit.edu> <7HY9P4G@xds13.ferranti.com> <1991Mar10.145908.10575@hawk.cs.ukans.edu>
Organization: Edinburgh University
Lines: 14

In article <1991Mar10.145908.10575@hawk.cs.ukans.edu> billk@hawk.cs.ukans.edu (Bill Kinnersley) writes:
>Definition of an interpreter: 
>   A case statement inside a do loop.

Corollary:  Most X programs are interpreters.

I think that some restrictions need to be placed on the way the output
depends on the input. Including a separation between "program" and
"input to program" and some sort of restrictions on the ways the program
may change at run time (basically so that the operative word is "change"
rather than "be created").
                                         ____
\/ o\ Paul Crowley aipdc@uk.ac.ed.castle \  /
/\__/ Part straight. Part gay. All queer. \/