History of Interpreted language

HomePage | Recent Changes | Preferences

	Revision 11 . . (edit) December 18, 2001 2:33 am by BenBaker *[adding more languages]**
	Revision 10 . . (edit) December 18, 2001 2:29 am by BenBaker
	Revision 9 . . December 18, 2001 1:53 am by Lee Daniel Crocker [Clarifying rewrite]
	Revision 8 . . December 18, 2001 1:32 am by Ed Poor [link to Java article, where I'm sure it's made clear that it's not interpreted]
	Revision 7 . . December 18, 2001 1:30 am by Lee Daniel Crocker [Java is /never/ interpreted. Bytecode (compiled from Java) is.]
	Revision 6 . . (edit) December 17, 2001 5:17 am by Hannes Hirzel
	Revision 5 . . December 16, 2001 4:09 am by Taw [copyedit]
	Revision 4 . . December 15, 2001 10:17 pm by Hagedis
	Revision 3 . . (edit) December 15, 2001 10:01 pm by Taw [/Talk]
	Revision 2 . . September 29, 2001 8:27 pm by Not now

Difference (from prior major revision) (minor diff, author diff)

Changed: 1,2c1,3

An interpreted language is kind of programming language, for which program's source code
is usually executed by interpreter, as opposed to being compiled by a compiler.

An interpreted language is kind of programming language designed to allow its
source code to be executed by an interpreter, as opposed to being compiled by a compiler
into object code.

Changed: 5,8c6,11

usually one method of use is dominant. Often there are some differences between what is
allowed in interpreted and what is allowed in compiled version of language.
For example compiled version might not allow eval statement,
or interpreter might prohibit using [inline assembler]?.

usually one method of use is dominant based on the language's design.
For example, many interpreted languages have a command such as Perl's eval,
which takes programming language text as data (which can be created at runtime) and
executes it, something that requires a language interpreter at runtime.
Languages designed for compilation, on the other hand, may have features like allowing
[inline assembly]?.

Changed: 10,11c13,15

Interpreted languages are generally slower, but can have many useful features that are difficult to
implement in a [compiled language]? - for example eval statement and platform-independence?.

Interpreted code generally runs more slowly that compiled code, but can have many useful
features that are difficult to implement in a [compiled language]?, for example the
aforementioned eval statement, platform-independence?, and interactivity.

Added: 12a17,20

Some languages like Perl and Python are designed to be interpretable, but are
often implemented by being compiled at runtime.
Other languages like UCSD Pascal and Java are designed for compilation, but
may be compiled into an intermediate bytecode form which is then interpreted.

Added: 14a23,24

* The original BASIC (though most modern versions are now compiled)

Added: 15a26

* Forth (traditionally threaded interpreted)

Added: 16a28,30

* Logo (interpretation makes interactivity easier)
* Lisp (traditionally interpreted, modern versions compiled)
* MUMPS (traditionally interpreted, modern versions compiled)

Removed: 20,21d33

Compare: Java