use strict;
no strict 'refs';
[download]

--

¤

Have a list of approved subroutines:

my %table = (
  fred => \&fred,
  barney => \&barney,
  betty => \&betty,
  wilma => \&wilma,
);
...
my $func = "betty";
$table{$func}->(@args); # call betty(@args);
[download]

This ensures that $func can't go wild and execute metafunctions that aren't part of the plan. And this does work under use strict.

-- Randal L. Schwartz, Perl hacker

I have had to use this mode of subroutine array referring before. I used no strict only around the calling statement. This worked, but I assume it does still raise a number of issues about the correctness of breaking 'strict' code.

{
    no strict;
    &$func_name(@list);
}
[download]

Normally using anonymous functions would be better for this. If the person wants to name their own function, they can construct the reference themselves.

The glaring exception is in places like AUTOLOAD routines where you are constructing the function on the fly, giving it a real name, and then calling that...