comment on

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);
[download]

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'
        ];
[download]

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks