Try either increasing your heap size (32Mg works pretty well),
or if all else fails break up your "large" lambda expression
into several smaller ones.

Whether your machine has 32Mg or 64Mg, doesn't affect this issue
since windows uses virtual memory. However the heapsize setting
in Allegro.ini provides a hard upper bound on the maximum size that
Allegro will grow the heap.

Ray,

________________________________________________________________________
Raymond de Lacaze					  <bbtech.com at ray>
Blackboard Technology Group, Inc.                  http://www.bbtech.com
401 Main Street                                      Phone: 413-256-8990
Amherst, MA  01002                                     Fax: 413-256-3179

On Mon, 3 Aug 1998, Richard Hibberd wrote:

> 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
>