Re: YA string concat proposal

Lightning flashed, thunder crashed and Garrett Goebel <garrett@scriptpro.com> w
hispered:
| cmp             ~<=>
| .=              ~+=
|                 ~=+ (concat after)
| =~              =~
| !~              !~

It's not bad enough that we're getting a proliferation of trigraph
operators, now you want to add a quadgraph?  No thank you.

Oh, and since it hasn't been mentioned for awhile, I'd still prefer if =~
and !~ went away and were replaced by match(string, [pattern], options),
replace(string, [pattern], options) and trans(string, ["pattern"], options)
or some such.  This is one place where I think PHP had a really good idea,
but missed the mark a little.  ereg_* and eregi_* and preg_* and pregi_*,
ugghhh...

-spp

• YA string concat proposal by Michael G Schwern
• Re: YA string concat proposal by Nathan Wiger
• Re: YA string concat proposal by Michael G Schwern
• Re: YA string concat proposal by Casey West
• Re: YA string concat proposal by Jonathan Scott Duff
• Re: YA string concat proposal by James Mastros
• Re: YA string concat proposal by Uri Guttman
• Re: YA string concat proposal by John Porter
• Re: YA string concat proposal by Nathan Wiger
• Re: YA string concat proposal by Jarkko Hietaniemi
• YA string concat proposal by Garrett Goebel
• Re: YA string concat proposal by Stephen P. Potter
• Regexp::Func (Re: YA string concat proposal) by Nathan Wiger