>>>>> "Richard" == Richard Fateman <fateman@cs.berkeley.edu> writes:
Richard> To move away from the display issue, consider another issue:
Richard> memory allocation. I think that GCL has certain problems in
Richard> this regard, and I don't know about CLISP or the offspring of
Richard> CMU lisp. If you run a problem and you find you have inadequate
Richard> stack to complete it, what do you have to do? Here are
Richard> the possibilities:
For CMUCL, you are out of luck if you run out of stack. In fact, CMUCL
conveniently crashes for you so you've lost everything.
And if you really need a bigger stack, you have to convince the CMUCL
guys to do a hairy cross-compile to increase it.
However, I think there's 128 MB of stack space and 1 GB or more of
heap, which is probably enough for any kind of problem I would expect
to run and finish in my lifetime. :-)
Ray