Since there were many answers on how to improve your regex handling, I thought perhaps a rearranging of the structure might help. This idea will be greatly affected by the size of the
@pairs array; also it is just an idea and I haven't benchmarked it.
# Get a hash of your translations, for quick lookup
%pair_lookup = map { chomp; split(/=/, $_, 2); } <SUBLIST>;
foreach $name (<CUSTLIST>) {
print NEWCUSTLIST
// split the line into words and check if there
// is a translation for it. If there is, return
// the translation otherwise return the original
join(" ", map { (defined $pair_lookup{$_})
? $pair_lookup{$_} : $_; }
split (/ /, $name, 2) );
}
Again this was just on the idea that there might be a way other than via a regex, and that it might be quicker.
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.