You can avoid magic stuff with a more cumbersome notation:

sub deep {SUB:{
++$count and --$_[ 0 ] and redo SUB; 
}}
[download]

Which is actually going to be faster afaik. (Havent tested though)

Yes, that does appear to be (crudely measured) about twice as fast, though it wouldn't work for mutally recursive subs.

#!/usr/bin/perl -w
use strict;
$|++;

my $count;

deep( $ARGV[ 0 ] );
print $count;

sub deep {SUB:{
++$count and --$_[ 0 ] and redo SUB;
}}

#sub deep {
#    ++$count and --$_[ 0 ] and goto \&deep;
#}
__DATA__
[20:54:56.63] P:\test>422344 10000000
10000000
[20:54:59.48] P:\test>422344 

[20:55:17.40] P:\test>422344 100000000
100000000
[20:55:41.24] P:\test>
[download]

---

Examine what is said, not who speaks.

Silence betokens consent.

Love the truth but pardon error.

Well, thats true I suppose but im not sure its entirely relevent, the tail recursion optimization only applies to subs which call themselves as the last statement. So insofar as the mutually recursive routines are tail recursive as well this optimization pattern still applies.

For those that dont know, (not you BrowserUK) tail optimization is really only _important_ in languages without looping constructs, in any language with looping constructs its just a nice bonus.

---
demerphq

From perlsyn:

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.

I've seen goto ⊂ ... I've never seen goto \⊂, which is what you did. Is there a difference?

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.