I've always found it useful to use indentation to indicate program calling depth. While it is very simple, that makes it easy to keep straight how many call frames are open at any point, and what they are. (All the statements from a particular call to the function should line up nicely.) 
#!/usr/bin/perl -w
use strict;

my $recursion = 0;

sub hanoi {
   my ($n, $start, $end, $extra) = @_;
   $recursion++;
   my $indent = "  " x $recursion;

   print $indent, "Entering hanoi($n, $start, $end, $extra)\n";

   if ($n == 1) {
       print $indent, "Move disk #1 from $start to $end.\n";
   } else {
        hanoi($n-1, $start, $extra, $end);
        print $indent, "Move disk #$n from $start to $end.\n";
        hanoi($n-1, $extra, $end, $start);
   }
   print $indent, "Leaving hanoi($n, $start, $end, $extra)\n";
   $recursion--;
}

hanoi(3, 'A', 'C', 'B');
__END__
  Entering hanoi(3, A, C, B)
    Entering hanoi(2, A, B, C)
      Entering hanoi(1, A, C, B)
      Move disk #1 from A to C.
      Leaving hanoi(1, A, C, B)
    Move disk #2 from A to B.
      Entering hanoi(1, C, B, A)
      Move disk #1 from C to B.
      Leaving hanoi(1, C, B, A)
    Leaving hanoi(2, A, B, C)
  Move disk #3 from A to C.
    Entering hanoi(2, B, C, A)
      Entering hanoi(1, B, A, C)
      Move disk #1 from B to A.
      Leaving hanoi(1, B, A, C)
    Move disk #2 from B to C.
      Entering hanoi(1, A, C, B)
      Move disk #1 from A to C.
      Leaving hanoi(1, A, C, B)
    Leaving hanoi(2, B, C, A)
  Leaving hanoi(3, A, C, B)

[download]
As the saying goes, to understand recursion you must first understand recursion. But hopefully this simple output will help you get that "ah hah!" moment where it starts to make sense.

In reply to Re: cannot follow hanoi subroutine by tilly
in thread cannot follow hanoi subroutine by convenientstore

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.