In the final program or script, you probably won't list all those file names, but you'll read them e.g. from a config file or even calculate them, which more or less will lead to a loop, like this
use 5.011; use warnings; use Data::Dumper; my $inputPathPrefix = "C:/Temp/xml"; my @inputfiles; for my $i (1..7) { push(@inputfiles, $inputPathPrefix . "/test${i}.xml"); } say Dumper(\@inputfiles);
gives
$VAR1 = [ 'C:/Temp/xml/test1.xml', 'C:/Temp/xml/test2.xml', 'C:/Temp/xml/test3.xml', 'C:/Temp/xml/test4.xml', 'C:/Temp/xml/test5.xml', 'C:/Temp/xml/test6.xml', 'C:/Temp/xml/test7.xml' ];
In a loop, push is more or less the only method.

BTW, you can also push multiple values in one go, see push


In reply to Re: Adding items to arrays: best approach? by soonix
in thread Adding items to arrays: best approach? by geertvc

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.