Re: RFC 165: Allow variables in a tr///

Lightning flashed, thunder crashed and Tom Christiansen <[email protected]
m> whispered:
| >The // tend to confuse people and make them expect tr to operate as a
| >regular expression.
| 
| So what?  q/.../ is not a "regex function" either.   These are all 
| pick-you-own-quotes function.  This makes no sense.

Personally, I would say that q/.../ and friends were a bad idea.  A lot of
non-gurus see /.../ (whatever comes before it) and their first impression
is that it has something to do with regex.  I would suggest that anything
that isn't a regex should not use /.../.  Make q, qq, etc use matched
pairs.  Make tr look like a regular function and do 
tr(SEARCH, REPLACE, MOD, STR).  It just seems more orthagonal to me.

-spp