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.
-
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.
|