I am building fairly large lambda expressions which contain a number of
macro calls, which again expand into quite large expressions; these will
sometimes generate the following

Error: Compiler ran out of space in EVAL.  HeapSize parameter in
allegro.ini may need to be increased and lisp restarted.

This is not unreasonable, but the threshold of expression complexity
that causes this appears to unrelated to both the heapsize parameter as
per the error message and also the RAM available to ACL.


I am running ACL-Win3.0 under Win95 with 64Mb, but the same occurs on
32Mb machines under both Win95 & NT4.0


Any thoughts?


Richard Hibberd

Department of Computing
Nottingham Trent University
U K