Re: RFC 165 (v1) Allow Varibles in tr///

Mark-Jason Dominus wrote:
>
> I think the reason this hasn't been done before it because it's *not*
> quite straightforward.

Before everyone gets tunnel vision, let me point out one thing:
Accepting variables in tr// makes no sense. It defeats the purpose of
tr/// - extremely fast, known transliterations.

tr///e is the same as s///g:

    tr/$foo/$bar/e  ==  s/$foo/$bar/g

I don't think this RFC accomplishes anything, personally.

-Nate