Of course the truly paranoid will make sure that it's a valid method first.

my $method = $q->param( 'method' ); # ... or whatever
if( my $m = $obj->can( $method ) ) {
  $obj->$m( @params );
} else {
  die "I can't call $method on a ", ref $obj;
}
[download]

beware of method names like "main::unsafe" for example. can() will return \&main::unsafe and not undef. this is also addressed in perlsec.pod.
better will be checking in a dispatch table in case $method comes from outside.

And the knowledgable would know that the extra code doesn't get you much, since calling an invalid method will die as it is...

The more knowledgeable would realize the die was just an example and that they could replace it with code which gracefully handles the problem (perhaps redirecting to an error page, or listing the valid methods).

Thanks!

This worked perfectly. I don't know what I was smoking! Maybe I just needed to tell someone else.

Sorry to bother the Monks with such trivialities…

   $quiz->$act()
[download]

use strict;
sub Foo::hello {
    shift; 
    printf "Hello, %s!\n", shift;
}

my $meth = "hello";
my $class = "Foo";
$class->$meth("world");
[download]

Method lookup is done at runtime. So, what's wrong with allowing an extra dereference?

It does bring up the point that $class->$meth() is not the same as $meth($class). (It is, however, the same as $class->can($meth)->($class). *grins*)

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

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.