Here is another complicated "perlish" solution to avoid simple C-style loops as proposed above (and which is the most sensible approach IMHO), this time using closures: 

se warnings;
use strict;

sub create_scheduler {
    my $list = shift;
    return sub {
        my $i = shift;
        return () if $i > $#$list - 1 or $i < 0;
        return ( $list->[$i], $list->[$i+1] );
    }
};

my $leg = create_scheduler [ "Chicago", "Saint Looey", "Joplin", "OKC"
+, "Amarillo", "Gallup", "Flagstaff", "Winona", "Kingman", "Barstow", 
+"San Bernandino", "LA" ];
 
my $i = 0;
while( my @pair = $leg->($i++) ) {
    print join( " to ", @pair ), "\n";
}

[download]

You could also "enclose" the index into the closure if you want to create a one-time iterator over your array.

In reply to Re: Fence vs. Posts by hdb
in thread Fence vs. Posts by rodinski

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.