Well, all direct text translations might be handled faster... but unless there is a lot of them compared to others then it probably won't help (might actually be slower). The actual help would be better to be tested as this is pure speculation :).
Basicly make to hashes instead of one. Something like this.
while (<REGEX>) {
chomp;
my ($key,$value) = split (\t,$_);
$value = "\"$value\"";
if ($key=~s/^\w+$/) {
$simple{$key}=$value;
} else {
$regex{$key}=$value;
}
}
while (<INPUT>) {
s/$key/$regex{$key}/gee foreach my $key (keys %regex);
foreach (split (/\s+/,$_)) {
if (exists($simple{$_})) {
push (@line,$simple{$_});
} else {
push (@line,$_);
}
}
print OUT "@line\n";
}
Note that in the given examples, you might write out the '
[Tt]ile' pattern to Tile and tile rows. Which would move it from slower pattern group to faster. But as I said, I'm not sure how much this would help.
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.