i don't know if this is faster or slower, but it seems like it would be easier to maintain if you built %DALPHA from %CALPHA and the same for %DDICT
my %CALPHA = (
'A' => [ 'wanker', 'tweet', 'bonk' ],
'B' => [ 'ping', 'zilch' ],
...
);
my %DALPHA;
foreach my $k ( keys %CALPHA ) {
foreach my $l ( @{$CALPHA{$k}} ) {
$DALPHA{$l} = $k;
}
}
then you just have to update one hash instead of two
if updates are frequent go a step further and pull them in from a DATA section.
...
while (my $l = <DATA>) {
my ($plain,$crypt) = split /\s+/, $l;
%CDICT{$plain} = $crypt;
%DDICT{$crypt} = $plain;
}
...
__DATA__
CORPS DIN-NEH-IH
DIVISION ASHIH-HI
REGIMENT TABAHA
...
you may have to use a different delimiter depending on your code.
HOT HEAD:DEF-DUM-DEE
CRUISE MISSILE:BOOM-BOOM
then you can add a new word way easy...
echo "JAR HEAD:UG-GO-GRUNT" >> /path/to/Crypt/Navajo.pm
cool anyways... now i can decode the blood-stained documents that mysteriously turned up in my mailbox
Update: merlyn is correct, i meant to say $CDICT{$plain}=$crypt; $DDICT{$crypt}=$plain;
-
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.