|Source code for a C interpreter email@example.com (1992-04-19)|
|Re: Source code for a C interpreter firstname.lastname@example.org (1992-04-20)|
|Re: Source code for a C interpreter email@example.com (1992-04-20)|
|Re: Source code for a C interpreter firstname.lastname@example.org (1992-04-20)|
|From:||email@example.com (Brian Bliss)|
|Keywords:||C, interpreter, FTP|
|Organization:||UIUC Center for Supercomputing Research and Development|
|Date:||Mon, 20 Apr 1992 17:06:21 GMT|
firstname.lastname@example.org (Jay Bookbinder) writes:
|> I am looking for C source code for a C interpreter ...
ftp to sp2.csrd.uiuc.edu and get /pub/at.tar.Z
uncompress, untar, & compile on a Sparc (cc or gcc) or Alliant FX or
ae (the "application executive") is a C interpreter library which is
compiled with an application; hence, the interpreter exists in the same
process and address space. it includes a dbx symbol table scanner to
access compiled vars & routines, or you can enter them manually by
providing a type/name declaration and the address. when the interpreter
is invoked, source code fragments are read from the input stream (or a
string), parsed, and evaluated immediately. The user can call compiled
functions in addition to a few built-in intrinsics, declare new data types
and data objects, etc. Different input streams can be evaluated in
parallel on alliant machines.
version 2 is in the works, and has been ported to the cray YMP. it
differs from version 1 in that the input stream is parsed into a tree
structure which is later evaluated, instead of the evaluation taking place
as the text is parsed.
Return to the
Search the comp.compilers archives again.