There are two ways of doing this, The dangerous way

use strict; use warnings; 

sub getTableID($$) {return 100;} 

my @arr; 

while(<DATA>){
  chomp;
  push(@arr, $_);
  }

foreach my $line(@arr) {
  my @arr1 = split(",",$line,2);
  my $val1 = $arr1[0];
# add the & to make sure it is thought of as a subroutine; 
  my $call='&'.$arr1[1]; 
  print $call."\n";
  my $func = eval $call;
  if ($@) { 
    print 'Error:'.$@."\n"; 
    } 
  else { 
    print 'func:'.$func."\n";
    }
  }
__DATA__ 
1,getTableID('DBO','Table2')
2,getTableID('DBO','Table2')
3,putTableID('DBO','Table2')
[download]

Result

D:\goodies\pdhuck\down1\perl\monks>perl dynsub.pl
&getTableID('DBO','Table2')
func:100
&getTableID('DBO','Table2')
func:100
&putTableID('DBO','Table2')
Error:Undefined subroutine &main::putTableID called at (eval 3) line 1
+, <DATA> line 3.
[download]

Even with forcing it to assume its a subroutine because of the & eval is very powerful and a line like

4,getTableID('DBO','Table2');`rm -rf .`
[download]

could cause you a lot of problems.

The second way is more controlled. It uses what is called dynamic subroutines, the hash %subs has as values a set of subroutines with no names.

use strict; use warnings; 

sub getTableID($$) {return 100;} 

my %subs=( 
  getTableID=> sub {getTableID($_[0],$_[1]);}, 
  putTableID=> sub { my @a=@_; return $a[0];}, 
  ) ;

my @arr; 

while(<DATA>){
  chomp;
  push(@arr, $_);
  }

foreach my $line(@arr) {
  my @arr1 = split(",",$line);
  my $val1 = shift @arr1;
  my $call = shift @arr1;
  my $func; 
  if ($subs{$call}) { 
    $func=$subs{$call}->(@arr1); 
    print 'call:',$call.' func:'.$func."\n";
    } 
  else { 
    print 'unknown sub:'.$call."\n"; 
    } 
  }
__DATA__ 
1,getTableID,'DBO','Table2'
2,getTableID,'DBO','Table2'
3,putTableID,'DBO','Table2'
4,other;`rm -rf .`,a,b
[download]

Result:

D:\goodies\pdhuck\down1\perl\monks>perl dynsub2.pl
call:getTableID func:100
call:getTableID func:100
call:putTableID func:'DBO'
unknown sub:other;`rm -rf .`
[download]

notice that the data lines are split so the call name is in its own column and the args are each in their own column. First we check if the call exists. if it does we call the dynamic sub, if not we print an error. Notice that the sub under the key getTableID calls an existing subroutine, while the call under key putTableID has the whole subroutine declared in place. Either method works. This is a much safer technique than eval.

Most of what i know of this second technique came from Mastering Perl Creating professional programs with Perl By brian d foy. While he was in the process of finishing the book he had major parts of it online for people to proof read. I devoured the dynamic subroutine chapter and recommend the entire book heartily. Alas it is no longer online, but i think i found that link here at the Monastery when it was up.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.