I'm pretty sure that this is not needed because you can't return to the source of a gotoIndeed, goto &foo pops the current call frame and replaces it with a new frame, rather than just pushing an additional one as a normal sub call would do. The following consumes lots of CPU but uses constant memory:
sub foo { goto &foo }; foo();
Dave.
In reply to Re^5: sub calls and memory use
by dave_the_m
in thread sub calls and memory use
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |