🚀 go-pugleaf

In article <9053@castle.ed.ac.uk> aipdc@castle.ed.ac.uk (Paul Crowley) writes:
>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").

    Why?  At what level of sophistication does a data processor become an
interpreter?  It's my fundamental belief that there IS no difference between
a language 'interpreter' and a data 'processor'.

    Perhaps it's ground that has been trodden over for millenia before I
came here, but is there a reasonable seperating ground between programs
and data?

                                                        --  Morgan Schweers
+-------------------------------------------------------------------------+
|     I *AM* ms@netcom.com and ms@albert.ai.mit.edu.  PLEASE try the first|
| address first.  My employers think I'm just another mindless AI program |
| without opinions...  Please don't try to convince them otherwise!       |
+-------------------------------------------------------------------------+