I think this is what you want:

#! perl -w use strict; use diagnostics; use Carp; sub iterFac { my $max = shift; my $val = shift || 1; my $cnt = shift || 1; Carp::cluck("we are currently here:"); return $val if $cnt > $max; #iterFac($max, $val*$cnt, ++$cnt); @_ = ($max, $val*$cnt, ++$cnt); goto &iterFac; } my $x = iterFac(5); print "Factorial 5 = $x\n";
Note how I've used Carp::cluck to show where we are at all times. If you remove the # from the iterFac call and comment out the @_ assignment and the goto, and run this, you'll see how it cluck's that it gets 5 subroutine calls deep. But as-is, the cluck always shows only a single subroutine deep.

I think that's what you're looking for, but someone with an actual CS degree may show me wrong ;-)


In reply to Re: Tail-recursion in perl?! by Tanktalus
in thread Tail-recursion in perl?! by neniro

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.