Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!rbj From: rbj@uunet.UU.NET (Root Boy Jim) Newsgroups: comp.lang.perl Subject: Re: Patterns vs Strings Message-ID: <121661@uunet.UU.NET> Date: 8 Feb 91 02:57:18 GMT References: <121642@uunet.UU.NET> <1991Feb07.210023.8308@convex.com> Organization: UUNET Communications Services, Falls Church, VA Lines: 33 In article <1991Feb07.210023.8308@convex.com> tchrist@convex.COM (Tom Christiansen) writes: >From the keyboard of rbj@uunet.UU.NET (Root Boy Jim): >:My experiments lead me to belive that >:whenever a "pattern" is expected, slashes >:are "promoted" to double quotes, as if "qq" >:had been stuck in front. > >I believe your observations to be correct... > >Note that if you use alternate delims on the match, like m#bar#, it still >gets qq// interpolated, unless you should use m'bar', in which case you >get q// action. I don't think you can use m`bar` for qx// action, but As merandalyn mentioned, quote type matters on s commands. However, m'$var' == m"$var" == m`$var`. And tr is brain dead. I have to use eval to get vars into either side. However, once again, I have not made myself clear. I am talking about the first argument to split and join. Normally, you can't just go passing strings to functions/operators by /quoting/ with slashes. And by "data types", I meant "string" vs "numeric". I know.... >neither can I think of why you'd ever want it to. Famous last words. >--tom -- Root Boy Jim Cottrell I got a head full of ideas They're driving me insane