Re: Using variables in array names

Yes, but you probably don't want to do it:

no strict 'refs';
my $point1 = 'valpt';
@$point1 = (1,2,3);
# symbolic reference
print @valpt;
[download]

Or (your specific request):

no strict 'refs';
my $point1 = 'valpt';
eval "\@use_$point1 = (1,2,3)";
print @use_valpt;
[download]

For several security and bug-hunting reasons, this is a very bad idea. What you probably want is a hash instead...

my $point1 = 'valpt';
my @array = (1,2,3);
$foo{ "use_$point1" } = \@array;
# hard reference to array stored in hash %foo
print @{ $foo{ 'use_valpt' } };
# dereference arrayref stored in %foo under 'use_valpt' key
[download]

You can then access your data by the name chosen in $point1 without worrying about creating global variables all over the place. Have a look at perlref.

Comment on Re: Using variables in array names Select or Download Code

Replies are listed 'Best First'.
Re^2: Using variables in array names by ikegami (Patriarch) on Aug 05, 2005 at 13:34 UTC
Why the eval??? `no strict 'refs'; my $point1 = 'valpt'; eval "\@use_$point1 = (1,2,3)"; print @use_valpt;` [download] can be written as: `no strict 'refs'; my $point1 = 'valpt'; @{"use_$point1"} = (1,2,3); print @use_valpt;` [download]	[reply] [d/l] [select]
Re^3: Using variables in array names by polypompholyx (Chaplain) on Aug 05, 2005 at 14:29 UTC
Because I am being particularly dim today. You're quite right: using `eval` is unnecessary, and may well be like handing a box of matches to a kid whose already playing with petrol. I shouldn't have mentioned it :)	[reply] [d/l]