Re^2: Return code from calling qx

The docs may explain it, but trying Googling for qq{perl "$? >> 8"} sometime. Google doesn't even honor the phrase so the results are not that impressive. On Google it's hard if not impossible to search for "$? >> 8? -- try it without "perl" and you will get links to the number 8 because Google is not searching on the phrase even though it is in quotes (probably too many special characters). One more reason not to like the five bazillion special two character variables Perl has (of course, when typing them in, most of us really like them! :-)

Elda Taluta; Sarks Sark; Ark Arks

Comment on Re^2: Return code from calling qx

Replies are listed 'Best First'.
Re^3: Return code from calling qx by ikegami (Patriarch) on Oct 28, 2009 at 03:13 UTC
I fail to see your point, especially since "special perl variables" turns up the very text I quoted in the first result.	[reply]
Re^4: Return code from calling qx by Argel (Prior) on Oct 28, 2009 at 18:29 UTC
Yes, but the OP was interested in what the ">>" line did, so he likely searched for something like "$? >> 8" -- and the results for that are not nearly as useful because Google doesn't treat that as a phrase. So while the docs do indeed clearly answer the question, the most obvious search at first glance will not take you to the docs. In other words, "The docs answers your question" would have sufficed -- no nead to use "clearly" and the negative connotations that it implies. Elda Taluta; Sarks Sark; Ark Arks	[reply]
Re^4: Return code from calling qx by SuicideJunkie (Vicar) on Oct 28, 2009 at 13:45 UTC
I see it as more of a complaint about Google's handling of special character searches. Such has annoyed me on many occasions too... I know exactly what I want to search for, but can't do a search on it to find the alternate ways to ask for it. ... if only Google had a perly regex mode...	[reply]