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

Lightning flashed, thunder crashed and Mark-Jason Dominus <[email protected]> whis
pered:
| 
| > 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)
| 
| MOD should be last, because you're frequently going to want to omit MOD.  

Ok, that's fine with me.

tr(SEARCH, REPLACE, STR, MOD)	- 'standard way'
tr(SEARCH, REPLACE, STR)	- 'no modifiers'
tr(SEARCH, REPLACE)		- 'no modifiers, and default to $_'
tr(SEARCH, REPLACE, $_, MOD)	- have to use all four if modifiers but $_
 
I just wasn't sure which would be omitted more often, the MOD or the STR.

-spp