On 2016-04-13, Christian Weisgerber <[email protected]> wrote: >> I'll just quote ksh.1: >> >> o Occurrences of \" inside double quoted `..` command substitutions. >> In POSIX mode, the \" is interpreted when the command is interpreted; >> in non-POSIX mode, the backslash is stripped before the command >> substitution is interpreted. For example, echo "`echo \"hi\"`" >> produces ``"hi"'' in POSIX mode, ``hi'' in non-POSIX mode. To avoid >> problems, use the $(...) form of command substitution. >> >> From time to time there's a configure script in ports that sets -o >> posix but expects the other behavior, because other popular shells >> do not share this interpretation of what POSIX mandates. bash, >> whether in POSIX mode or not, and FreeBSD's sh always strip the >> backslashes. >> >> On reading the POSIX text, I find the ksh author's interpretation >> far-fetched. See also: >> http://austingroupbugs.net/view.php?id=1015 >> >> Regardless of what you contend the standard text says, I think it >> is clear that the other interpretation has won out in practice and >> I propose to align our ksh with that: > > This has now successfully passed a bulk package build. -snip-
I have received an ok from a single senior developer, but no reactions from any other developers at all. -- Christian "naddy" Weisgerber [email protected]
