magic/lisp
Darryl L. Miles 3aebbbd038 Makefile: various consistency matters
Using defined variables ${RM} for common tools
error handling
ensuring default target (is not install)
2025-07-29 10:50:32 -04:00
..
scm Convert $Id$ placeholders to $Header$ placeholders. 2020-05-23 17:00:38 -04:00
Makefile Makefile: various consistency matters 2025-07-29 10:50:32 -04:00
README Convert $Id$ placeholders to $Header$ placeholders. 2020-05-23 17:00:38 -04:00
lisp.h Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispA-Z.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispA-Z.h Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispArith.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispEval.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispFrame.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispGC.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispIO.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispInt.h Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispMagic.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispMain.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispParse.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispPrint.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispString.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispTrace.c Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00
lispargs.h Updates from running the fix-ending-whitespace script. 2020-05-23 17:13:14 -04:00

README

This is a mini-scheme interpreter, even though the files are all named
lisp*.{c,h}.

This interpreter is *extremely* slow. I can think of lots of ways to
improve its memory usage and performance (a factor of 5 improvement
seems easy), but it is very robust and it works. :) Besides, it turns
out that the bottleneck in most common tasks is magic itself, not the
interpreter.

The memory usage of this interpreter is ridiculously high. Collect garbage
often. :) Garbage collection is done automatically based on the
variable scm-gc-frequency at the top-level . . . i.e., when you see
magic's ">" prompt. To collect garbage at intermediate points in the
computation, you have to call "collect-garbage" explicitly.


-Rajit Manohar <rajit@csl.cornell.edu>
 Computer Systems Laboratory
 Cornell University
 Ithaca NY 14853
 http://www.csl.cornell.edu/~rajit/

$Header$