Your bug is that you are initializing your arrays with:
my @polea = ""; my @poleb = ""; my @polec = "";
which means that they have invisible 0-width entries on top of each stack. Get rid of those and your bug goes away.

Incidentally if you change the way you print slightly, you can turn warnings back on:

for (my $len = 0 ;$len <= $numdisks; $len++) { print join "\t\t\t", map {$_->[$len] || ""} \@polea, \@poleb, \@po +lec; print "\n"; }
(You have to change this in two locations.)

In reply to Re: A quandry in Towers of Hanoi by tilly
in thread A quandry in Towers of Hanoi by pmonk4ever

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.