Re: Overlapping RFCs 135 138 164

2000-08-29 Thread Stephen P. Potter
Lightning flashed, thunder crashed and Mark-Jason Dominus <[EMAIL PROTECTED]> whis pered: | | RFC135: Require explicit m on matches, even with ?? and // as delimiters. | | RFC138: Eliminate =~ operator. | | RFC164: Replace =~, !~, m//, and s/// with match() and subst() | | I would like to see

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

2000-08-29 Thread Stephen P. Potter
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. 2) Remove y/// as a command. -spp

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

2000-08-29 Thread Stephen P. Potter
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 ma

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

2000-08-29 Thread Stephen P. Potter
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

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

2000-08-29 Thread Stephen P. Potter
Lightning flashed, thunder crashed and Mark-Jason Dominus <[EMAIL PROTECTED]> whis pered: | > > The way tr/// works is that a 256-byte table is constructed at compile | > > time that say for each input character what output character is | > | > Speaking of which, what's going to happen when there

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

2000-08-30 Thread Stephen P. Potter
Lightning flashed, thunder crashed and Tom Christiansen <[EMAIL PROTECTED] m> whispered: | >Personally, I would say that q/.../ and friends were a bad idea. | | That's one opinion. As Piers points out, it's hardly universal. | Go read what I just wrote Uri. "Personally" generally denotes opin

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

2000-08-30 Thread Stephen P. Potter
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

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

2000-08-30 Thread Stephen P. Potter
Lightning flashed, thunder crashed and Bart Lateur <[EMAIL PROTECTED]> whis pered: | Speedwise, it is. You don't have to do any tests on the bytes. All you | have to do is use the ord of the character (the byte value) as an offset | in a table, and replace what you had with what you find in the ta

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

2000-08-30 Thread Stephen P. Potter
Lightning flashed, thunder crashed and Mark-Jason Dominus <[EMAIL PROTECTED]> whis pered: | I don't understand what this discussion has to do with this mailing | list, and I don't understand what your point is. tr/// has already This discussion doesn't have anything to do with this list. They w