>Would there be any interest in adding these two ideas to this RFC: >1) tr is not regex function, so it should be regularized to > tr(SEARCH, REPLACE, MOD, STR) >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. --tom
- Re: RFC 165: Allow variables in a tr/// Stephen P. Potter
- Re: RFC 165: Allow variables in a tr/// Mark-Jason Dominus
- Re: RFC 165: Allow variables in a tr/// Nathan Wiger
- Re: RFC 165: Allow variables in a tr/// Tom Christiansen
- Re: RFC 165: Allow variables in a tr//... Nathan Wiger
- Re: RFC 165: Allow variables in a tr/// Tom Christiansen
- Re: RFC 165: Allow variables in a tr/// Mark-Jason Dominus
- Re: RFC 165: Allow variables in a tr//... Tom Christiansen
- Re: RFC 165: Allow variables in a... Mark-Jason Dominus
- Re: RFC 165: Allow variables in a tr/// Stephen P. Potter
- Re: RFC 165: Allow variables in a tr/// Tom Christiansen
- Re: RFC 165: Allow variables in a tr/// Stephen P. Potter
- Re: RFC 165: Allow variables in a tr/// Piers Cawley
- Re: RFC 165: Allow variables in a tr/// Bart Lateur
- Re: RFC 165: Allow variables in a tr/// Tom Christiansen
- Re: RFC 165: Allow variables in a tr//... Stephen P. Potter
- Re: RFC 165: Allow variables in a... Tom Christiansen
- Re: RFC 165: Allow variables in a tr/// Eric Roode