Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re^3: Bug in perl command line processing?

by Anonymous Monk
on May 22, 2012 at 21:38 UTC ( #971885=note: print w/ replies, xml ) Need Help??


in reply to Re^2: Bug in perl command line processing?
in thread Bug in perl command line processing?

This completely misses the point.

Not it doesn't , the point of a "SEE ALSO" section is to "SEE ALSO"

The OP doesn't even specify what shell he is dealing with, and this is shell quoting territory


Comment on Re^3: Bug in perl command line processing?
Re^4: Bug in perl command line processing?
by sauoq (Abbot) on May 22, 2012 at 21:45 UTC

    Now you've missed the point twice.

    FWIW, it works on Windows as well, with suitable quoting, of course.

    -sauoq
    "My two cents aren't worth a dime.";

      Now you've missed the point twice.

      Nope. Even if this is a bug in perl, you're still dealing with a shell, so a SEE ALSO cannot possibly miss the point

        Even if this is a bug in perl, you're still dealing with a shell

        So, every time there is ever a bug with any unix command line program, you'll think it appropriate to link to some guide on shell quoting?

        wtf-ever.

        Anyone with enough clue to really understand and be interested by this in the first place, doesn't need a refresher on basics.

        Why have you chosen to post anonymously?

        Never mind. That's a rhetorical question.

        -sauoq
        "My two cents aren't worth a dime.";
Re^4: Bug in perl command line processing?
by EvanCarroll (Chaplain) on May 22, 2012 at 21:47 UTC
    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

      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?

        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
Re^4: Bug in perl command line processing?
by demerphq (Chancellor) on May 22, 2012 at 21:47 UTC

    I'd have thought the same thing if it weren't that it works even tho there is no '-' on the 'e', which says to me its not purely the shell playing tricks on us. Anyway, I can replicate in bash.

    ---
    $world=~s/war/peace/g

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://971885]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (8)
As of 2014-09-19 19:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (145 votes), past polls