> This is how I interpreted POSIX's requirement that quoted strings
> inside backquotes be recursively processed:
My interpretation differs from yours, in order to match traditional behavior.
>
> "While processing the characters, if instances of expansions or quoting
> are found nested within th
Oliver Kiddle wrote:
> Is it intentional that the following script, which worked in 2.05b now
> produces errors in 3.1:
>
> : `: "\\""`
>
> That now results in: unexpected EOF while looking for matching ``'
> Using a third backslash fixes it but this is inconsistent with ash bash2
> bsh ksh pdksh
> Is it intentional that the following script, which worked in 2.05b now
> produces errors in 3.1:
>
> : `: "\\""`
>
> That now results in: unexpected EOF while looking for matching ``'
> Using a third backslash fixes it but this is inconsistent with ash bash2
> bsh ksh pdksh and zsh.
No, it is
>
> Your interpretation has evolved. Consider
> http://lists.gnu.org/archive/html/bug-bash/2005-07/msg00047.html
> when you argue seemingly the exact opposite: that quoted strings should
> be recursively parsed inside ``.
Perhaps it has. But in that mail from last year, the string in question w
Is it intentional that the following script, which worked in 2.05b now
produces errors in 3.1:
: `: "\\""`
That now results in: unexpected EOF while looking for matching ``'
Using a third backslash fixes it but this is inconsistent with ash bash2
bsh ksh pdksh and zsh.
Oliver
This e-mail and a
