Re: stack size info

[Stefan Monnier]

>    I don't think so.  My guess is "The maximum stack size this function
>    needs for execution, disregarding further (including recursive)
>    function calls as those extend the stack on their own."

> i'm inclined to leave the docs alone.  the node's entire context is a
> single function and thus the STACKSIZE element of the byte-code function
> object pertains to a single function call.

> however, if pressed, i will suggest:
> The maximum stack size this function might need when called.

> "might" because it is possible that any particular call uses less than
> that amount.  "when called" addresses recursion.

Maybe it could be called a "stack frame".
And I'd use the word "upper bound" rather than maximum.
Also I'd use the word "use" rather than "need".


        Stefan