You could have written the original loop as: 
for (map("arg$_", 1..5)) {
  ..
}

[download]
That was my first though, but on further reflection, it looks like configuration information (i.e., which form fields we're interested in) is getting mixed into the code. Is this a bad thing? Perhaps. If the fact that we're interested into "arg1" .. "arg5" (and might later be interested in "arg19" or "gee37") appears elsewhere in the code, then lifting that information out into a configuration section would make maintenance safer.   my @formArgs = map { "arg$_" } 1..5; and then, later in the code 
  foreach ( @formArgs ) {
    ..
  }

[download]

In reply to Re: •Re: On Foreach Loops and Maintainability by dws
in thread On Foreach Loops and Maintainability by rob_au

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.