In addition to the points made by Ovid, Perl-style foreach loops are a lot less error prone than C-style for loops are.

People who use C-style loops, whether it be in C or another language, typically have off-by-one errors as their most common type of bug. By simply switching to Perl-style loops when programming in Perl, you kill the opportunity for this mistake, and therefore will have fewer bugs to track down.

I have seen this happen in enough cases that I can't accept the argument that it is simply personal preference. When you have a choice, use the Perlish looping mechanism. The time saved in avoiding debugging will quickly make this pay for itself.

In reply to Re (tilly) 3: Newbie realisation about by tilly
in thread Newbie realisation about by Cody Pendant

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.