tr/// is only going to help you if all of your transformations are 1:1 in terms of chars. If there are any examples of 1:N then its not going to help you. IE, if you need to convert chars with umlouts to their non-umlaut equivelents then tr/// wont help you. As for it being faster im surprised there was any question. Especially with the code you are using. join/map/split is a pretty horrible way to handle this. If i had to use a hash id do something like s/([...])/$map{$1}/g which is isnt going to be faster than tr/// but will certainly be faster than join/map/split.

---
$world=~s/war/peace/g

In reply to Re: The indisputable speed of tr/// by demerphq
in thread The indisputable speed of tr/// by radiantmatrix

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.