I would use a dispatch table with a bunch of subroutines, one for each action. The dispatch table makes it easy to use the command line argument to call the proper bit of code. Simple example:
my %ACTION_NAMED = define_actions();
my $action = shift; # First argument
my @args = @ARGV; # Remaining arguments
if (exists $ACTION_NAMED{$action}) {
$ACTION_NAMED{$action}->(@args);
}
else {
$ACTION_NAMED{_default_}->(@args);
}
sub define_actions {
return (
action1 => \&action1,
action2 => \&action2,
_default_ => \&usage,
);
}
sub action1 { ... }
sub action2 { ... }
sub usage { ... }
-
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.
|