Tony Balinski - 2005-10-04

Logged In: YES
user_id=618141

That's right. It's a limitation of the way macro string
memory is managed. Essentially, macro memory is only freed
once there are no more running macros. For short macros this
is not a problem. For larger ones (particularly where lots
of small bits are accumulated into a big string) it can
cause severe memory shortages. I have detab/retab macros
which suffer from this.

I got about 2/3 of the way to replacing the macro string
memory management, rewriting a lot of interpret.c and
macro.c. I should brush the dust off it and get it all to work!