This sounds very familiar. I bet I'll find that the handler (count_up) is called using MULTICALL. The last time I looked at it, I hypothesised that MULTICALL is an optimization used to speed up calling a function repeatedly by reusing stack frames, and that it fails when a lexical is still referenced when it goes out of scope.
In reply to Re: Odd lexical variable behavior -- why does this happen?
by ikegami
in thread Odd lexical variable behavior -- why does this happen?
by radiantmatrix
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |