G'day hexcoder,
Perhaps, instead of a table of just templates, you could use a table of coderefs
whose functionality includes preprocessing, unpacking, formatting, and anything else you need.
Here's a highly contrived and primitive example just to show the technique.
#!/usr/bin/env perl -l
use strict;
use warnings;
my %decode_type = (
A => sub { "Do TypeA stuff with '$_[0]'" },
B => sub { "Do TypeB stuff with '$_[0]'" },
);
while (<DATA>) {
chomp;
my ($type, $msg) = split /\s+/, $_, 2;
my $decoded = $decode_type{$type}->($msg);
print $decoded;
}
__DATA__
B message B1
A more complex message A1
B message B2
Output:
Do TypeB stuff with 'message B1'
Do TypeA stuff with 'more complex message A1'
Do TypeB stuff with 'message B2'
I don't know how useful that might be; however,
your general description suggested this approach.
-
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.
|