for my $i (0 .. $MAX_ROWS - 1) {
    push @fee, ${"foo_$i"};
}
[download]

That said, DON'T DO IT THAT WAY.

That is what's called a "soft reference". Since you're coming from the web, you should know it's a security leak. Taint-checking fails that. strict fails that. (You are using string and -T, right?)

As for a better solution, you need to change your form. CGI should be able to handle arrays. (You are using CGI, right?)

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

my $local_foo = ${"foo_$i"}
[download]

my @fee;
for (0 .. $MAX_ROWS){
   push @fee, $foo[$_];
}
[download]

my @fee = @foo[0 .. $MAX_ROWS];
[download]

_________
broquaint

You can create variables dynamically, true. But that's not actually what you need here. When ever you have a series of scalars with trailing integers, use an array, and then you can access the array elements in your for loop. Also, using foreach is more idiomatic (which is a fancy word for "better written")

@foo = ('foo0', 'foo1', 'foo2', 'foo3');
foreach $member (@foo) {
    push @fee, $member;
}
[download]

Light a man a fire, he's warm for a day. Catch a man on fire, and he's warm for the rest of his life. - Terry Pratchet

()-()
 \"/
  `                                                     

I'm trying to do something like this:
my @fee;
for (my $i=0; $i < $MAX_ROWS; $i++){
   my $eval_str = "push @fee, \$foo_$i";
   eval($eval_str);
}#end loop
[download]

Except from the fact the eval contains a syntax error (you'd need to escape the @), what makes you think the eval is unsafe? There's no data coming from the outside. The eval is as safe as any other code from the programmer.

There's a lot that can be argued against "variable names inside variable names", but security is only an argument if you use data from the untrusted environment as variable names.

Abigail

... but security is only an argument if you use data from the untrusted environment as variable names.

Really?

Whenever code does not behave as expected, there is a real possibility of an unexpected consequence that compromises security. Therefore any programming practice that leads to bugs is also a source of potential security flaws, even if it is not obvious how to get there.

A return question for you: what stops you from using an array and $foo[1]...$foo[100] instead of $foo_#?</code>

If you could use an array, say @foo, the problem of putting everything in @fee disappears... what I can't really get is how and why your variables from the form are named that way...

In any case, you probabily need to take a look at CGI.pm

Ciao!
--bronto

# Another Perl edition of a song:
# The End, by The Beatles
END {
  $you->take($love) eq $you->made($love) ;
}