On 4/27/21 6:52 AM, jr wrote:
Played a few minutes with this just now and you can get your original
code to run if you change the tail m_l10 macro to:
#debug concat("----------> level 10, n = ",str(n_,0,0),".\n")
#fopen FID "parse_fore.tmp" write
Though by the time it finishes it's consumed 1.6G or more of memory
after maybe five minutes. My wild guess is all those Parse_String(s) end
up sitting in memory until parsing is finished. In other words I think
at the end we have unrolled more or less the whole recursion.
Parse_String is involved in what's happening, but it's not clear to me,
why - some scope issue maybe as it comes after the last "call" to m_l10.
Post a reply to this message