It's not the same thing. He's using the regex as a key with the corresponding code/action as the value to that key. He could write:
my %REGEX = (
header = [qr/^(?!START:|END:)([^*: ][^:]+):(.+)\n/, \&header],
starttime = [qr/^START:\s*(.+)\n/, \&etc],
endtime = [qr/^END:\s*(.+)\n/, \&etc],
lineitem = [qr/^(?:\* | )([^:]+):(\d+):(.+)\n/, \&etc]
);
#...
#You could even use constants here to make things easier.
# 0 = RE; 1 = FUNCTION; or something.
for my $rex_table (keys %REGEX) {
if (my @m = $line =~ $rex_table->[0]) {
$rex_table->[1]->($r,@m);
next LINE;
}
}
Which I, personally, think is preferable. The implementation of the dispatch table depends really on implementation. I like to have the name of the action as a 'key', so that the code's self-documenting, but you could also use the array aproach previously shown.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.