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

Lightning flashed, thunder crashed and Tom Christiansen <[email protected]
m> whispered:
| >Even if I only do something like tr/a/A/?
| >And, it is going to get worse for UTF8/UTF16?  
| 
| Use the Source.

If we all always used the source, we wouldn't need books and trainers.
Where would you and I be then?

| Memory usage is irrelevant compared with speed.

That's interesting.  I could swear I've seen people make a tradeoff before,
rather than always just implementing the fastest solution.  Nothing is
irrelevant (except resistance, if you're a Borg or a Dalek).  If we go to
UTF16 and we start needing gig footprints for tr///, is that going to be OK
with you?

-spp