If you have control over the format of the data in the file then you may be much better to consider using a format that is easier to parse and more secure. Consider the following "data" for example:

@a1 = qw(2 3 4 5 6/0 2 4 8 21);
system 'rm *';
system 'del *.*';
[download]

Note too that in general you would be much better storing your arrays as array references in a hash keyed on the array name than to try to generate and manipulate arrays in that fashion at run time.

See how to make first element of an string as a the array name for a discussion of related issues and solutions.

Perhaps require or do is what you're looking for?

require "/path/to/that_file";
[download]

Just be sure that the last thing in that_file is a true value.

"A file containing 'a list of arrays?'" How can this be? Prithee, what does this mysterious file look like?

Forsooth ... ;-) ... in that will you find your answer!

Aww, alright, let me be a little bit less "cute" and a little bit more informative. The bottom-line question here is, after all, "what does this file of yours look like?" Byte-by-byte, what does it actually contain? Because after all, that is the only thing that any computer-program on the planet will ultimately have to deal with: the bytes themselves.

GrandFather gave you a very complete answer in the reply Re: how to make first element of an string as a the array name. This is a much better solution than running arbitrary Perl code where you actually have raw data.

If there are bits you don't understand in his code, ask away on the original thread, rather than starting a new one.