On Thu Nov 12 10:25:43 2015, public@khwilliamson.com wrote: > It seems to me to be the best short term thing to forbid tr/// in > utf8_heavy.pl. This was a micro optimization, after all. I find it > hard to believe that using tr/// over s/// makes a significant time > difference. It would be easy to write a fast porting test that makes > sure there aren't tr's in utf8_heavy.pl, so that the minefield is > avoided. Perhaps something like the attached. Tony --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=126593