|Do you know where your variables are?|
Re^7: Who's a thief? (No memory growth with magic goto)by BrowserUk (Pope)
|on Jan 14, 2005 at 20:54 UTC||Need Help??|
The goto-&NAME form is highly magical, and substitutes a call to the named subroutine for the currently running subroutine
Limbic~Region's post referenced a post by TimToady which will give the real skinny of how it works, but it does avoid the stack growth at the penalty of requiring the programmer to arrange for the algorithm to be tail-recursive.
You can use closures to provide yourself with one or more "stacks" if that is required. By controlling what gets stacked and when, even some non-tail recursive algorithms can benefit from reduced memory consumption and greater speed. It is especially useful for mutually recursive algorithms that need to share intermediate results.
That takes some effort, but if you have an inherently recursive algorithm that lends itself to that process, and a need for speed, then it can be worth it.
Examine what is said, not who speaks.
Silence betokens consent.
Love the truth but pardon error.