Clinton A. Pierce <[EMAIL PROTECTED]> wrote: > Found the bug. Mostly MEA CULPA. A thousand pardons to the good Parrot folk.
> When calling a sub like this: > .arg 0 > call _foo > It's probably a good thing to take the 0 off the stack at some > point. Thanks again for your bug report and thorough checking all kind of parrot limits. I've added a check for too deeply nested stacks now. Your first test program now bails out at: 25342 Stack 'User' too deep The limit is currently fixed at 100 chunks, but could easily be changed with a new opcode, e.g. stack_limit <.Stack>, limit. The stack_height() call could also be optimized then as well as other code pieces which are walking the stack from the base. leo
