elTriberium:
It's really pretty simple to use a dispatch table, so no module is really required. For example:
$ cat disp_tbl.pl
#!/usr/bin/perl
use strict;
use warnings;
use feature ':5.10';
sub foo { say "foobar" }
sub bar { say "barbaz" }
my %DT = ( foo=>\&foo, bar=>\&bar, quit=>sub { die "END!"; } );
say "Commands are foo, bar and quit\n";
while (<>) {
chomp;
if (exists $DT{$_}) {
$DT{$_}();
}
}
$ perl disp_tbl.pl
Commands are foo, bar and quit
foo
foobar
bar
barbaz
quit
END! at disp_tbl.pl line 9, <> line 3.
Update: By themselves, dispatch tables aren't a security concern. As long as the user isn't able to have perl (or the shell, database...) execute a string that the user enters, then everything is under the programs control.
Update: Ooops! mr_mischief mentioned that very thing as I was editing my node.
...roboticus
When your only tool is a hammer, all problems look like your thumb.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|