Related articles |
---|
What is an interpreter? tdarcos@mcimail.com (Paul Robinson) (1993-05-08) |
Re: What is an interpreter? prener@watson.ibm.com (1993-05-09) |
Re: What is an interpreter? haahr@adobe.com (1993-05-09) |
Re: What is an interpreter? monnier+@cs.cmu.edu (1993-05-10) |
Re: What is an interpreter? mleone+@cs.cmu.edu (1993-05-10) |
Re: What is an interpreter? macrakis@osf.org (1993-05-11) |
Re: What is an interpreter? khattra@cs.sfu.ca (1993-05-13) |
Newsgroups: | comp.compilers |
From: | mleone+@cs.cmu.edu (Mark Leone) |
Keywords: | interpreter, design |
Organization: | School of Computer Science, Carnegie Mellon |
References: | 93-05-039 |
Date: | Mon, 10 May 1993 15:55:17 GMT |
Paul Robinson <tdarcos@mcimail.com> writes:
>How do we determine when
>something is a "real" interpreter of a "real" language, and when it
>doesn't quite reach that point?
Since this is a pedantic exercise, here's a pedantic answer: Turing
equivalence. All other useful language features can be simulated.
>File I/O, I think is the knife that cuts the "toys" from the "real"
>languages.
This would be useless in a language without some control features,
like iteration or functions.
In general, "perceived utility" is a bad way to classify languages
(or interpreters), because people disagree on what features are useful.
--
Mark Leone <mleone@cs.cmu.edu>
School of Computer Science, Carnegie Mellon University
Pittsburgh, PA 15213 USA
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.