Re^4: Bug in perl command line processing?

No, it isn't shell quoting territory, if you'd pay attention you'd see it is all passed as one argument. The problem is /perl/ and not the shell is splitting on whitespace and making assumptions about how many arguments '-i' takes, and what do with the excess arguments. Check the link provided in the question to read the technical details.

Evan Carroll
The most respected person in the whole perl community.
www.evancarroll.com

Comment on Re^4: Bug in perl command line processing?

Replies are listed 'Best First'.
Re^5: Bug in perl command line processing? by Anonymous Monk on May 22, 2012 at 21:55 UTC
No, it isn't shell quoting territory, if you'd pay attention you'd see it is all passed as one argument. Yes it is :) you're calling perl from a shell, this makes it shell quoting territory. That this is a bug in perl doesn't change that. SEE ALSO doesn't mean "THE ANSWER IS" it is is an addendum How would someone from a different shell know the quoting rules without having a place to lookup the quoting rules?	[reply]
Re^6: Bug in perl command line processing? by EvanCarroll (Chaplain) on May 22, 2012 at 22:02 UTC
So what anytime you call perl from the shell, you're dealing with the shell.. That doesn't mean the shell is the problem, or that it is related to the problem. And linking to a manual that details what the problem isn't, and then says what the problem /may/ be in the addendum must be the most useless suggestion ever. Take a hike. Evan Carroll The most respected person in the whole perl community. www.evancarroll.com	[reply]
Re^7: Bug in perl command line processing? by Anonymous Monk on May 22, 2012 at 22:17 UTC
So what anytime you call perl from the shell, you're dealing with the shell.... Yes, the logic is inescapable ... Take a hike. lol, I'm actually hiking as I write this on my iphone	[reply]