in reply to Re: Splitting up quoted/escaped command line arguments
in thread Splitting up quoted/escaped command line arguments

Without knowing the name for it, I have already started trying to put together a state machine. I called it a "peel off" approach where I look through the string and peel things off one at a time, making sure to note and handle quoted things when I encounter them. I haven't got very far with it yet--just a few minutes working on the idea.

Tommy
A mistake can be valuable or costly, depending on how faithfully you pursue correction

Replies are listed 'Best First'.
Re^3: Splitting up quoted/escaped command line arguments
by Tommy (Chaplain) on Feb 11, 2014 at 19:31 UTC

    OK. This mixture of approaches seems to be working so far: I haven't been able to break it yet. Can anyone break this?

    (Please see UPDATE 2 to the OP)

    Tommy
    A mistake can be valuable or costly, depending on how faithfully you pursue correction
[reply]
      'a'\''b' Seems to break update 4.
      لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ
[reply]
[d/l]

        That's ok with me, because in Linux-ese (bash/sh/ksh), you can't escape a single quote. It's one of the most annoying things and I find it reeeally bothersome. This is why I don't try to accommodate for a "\'" sequence in update 4. Despite the fact that I don't want these commands to go to the shell, they are being written by people who deal with the shell almost exclusively: system admins. This much I can assume: that they won't be putting in commands that have syntax which outright fails to run on its own.

        Tommy
        A mistake can be valuable or costly, depending on how faithfully you pursue correction
[reply]
[d/l]

In Section Seekers of Perl Wisdom