TPIPE: unbalanced escaped quotes in a regex?

[vefatica]

Neither Onig or a number of Gnu text utilities are bothered by unbalanced escaped quotes in a regular expression. But TPIPE seems to be. Below, in the second example, I replaced the first \" with just . (dot). What's up with that?

v:\> echo "foo" | tpipe /replace=4,1,0,1,0,0,0,0,0,"\"(.*)\"","$1"
foo

v:\> echo "foo" | tpipe /replace=4,1,0,1,0,0,0,0,0,".(.*)\"","$1"
TPIPE: The parameter is incorrect.
"".(.*)\"","$1""

 

[samintz]

I noticed something similar with @regexsub. It fails to match the quote and then fails to match anything - i.e. it returns an empty string.

 

[vefatica]

I noticed something similar with @regexsub. It fails to match the quote and then fails to match anything - i.e. it returns an empty string.

@REGEXSUB (Onig) seems OK to me.

v:\> echo %@regexsub[1,\"(.*)\","foo"]
foo

v:\> echo %@regexsub[1,.(.*)\","foo"]
foo

v:\> echo %@regexsub[1,\"(.*).,"foo"]
foo

 

[rconn]

Neither Onig or a number of Gnu text utilities are bothered by unbalanced escaped quotes in a regular expression. But TPIPE seems to be. Below, in the second example, I replaced the first \" with just . (dot). What's up with that?

WAD - TPIPE has to extract the individual arguments, and it can't do that with mismatched quotes.

 

[AnrDaemon]

You're using wrong quoting character in command line.
TCC is not bash, and quoting character is not a backslash.

Everyone quotes command line arguments the wrong way

blogs.msdn.microsoft.com

 

[vefatica]

You're using wrong quoting character in command line.
TCC is not bash, and quoting character is not a backslash.

The backslash is the escape character for Perl regular expressions.