This is a little clumsy, but you could have '?' => 'HELP', etc, then use a loop at startup that replaced non-code refs with the code ref of the hash indice the value side points to.
It doesn't completely solve the semantic problem, but if you rename a routine, you only have to touch it one place, and adding synonyms becomes trivial.
#!/usr/local/bin/perl -w
use strict;
my %hash = ('HELP' => \&do_help,
'?' => 'HELP',
'LIST' => \&do_list,
'SHOW' => 'LIST',
'TEST' => \&do_test,
);
{
while (my ($k, $v) = each (%hash))
{
$hash {$k} = $hash {$v} if (ref $hash {$k} ne 'CODE');
}
&{$hash {'HELP'}};
&{$hash {'?'}};
&{$hash {'LIST'}};
&{$hash {'SHOW'}};
&{$hash {'TEST'}};
}
sub do_help {print "help\n"}
sub do_list {print "list\n"}
sub do_test {print "test\n"}
--Chris
e-mail jcwren
-
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.
|