ba02a307fe
If a command substitution contains a newline token, this no longer starts here documents of outer commands. This way, we follow POSIX's idea of the command substitution being a separate script more closely. It also matches other shells better and is consistent with newline characters in quotes not starting here documents. The extension tested in parser/heredoc3.0 ($(cat <<EOF)\ntext\nEOF\n) continues to be supported. In particular, this change allows things like cat <<EOF && echo `pwd` (a `` command substitution after a here document) which formerly silently used an empty file as the here document, because the EOF of the inner command "pwd" also forced an empty here document.
45 lines
431 B
Plaintext
45 lines
431 B
Plaintext
# $FreeBSD$
|
|
|
|
failures=0
|
|
|
|
check() {
|
|
if ! eval "[ $* ]"; then
|
|
echo "Failed: $*"
|
|
: $((failures += 1))
|
|
fi
|
|
}
|
|
|
|
f() {
|
|
cat <<EOF && echo `echo bar`
|
|
foo
|
|
EOF
|
|
}
|
|
check '"`f`" = "foo
|
|
bar"'
|
|
|
|
f() {
|
|
cat <<EOF && echo $(echo bar)
|
|
foo
|
|
EOF
|
|
}
|
|
check '"$(f)" = "foo
|
|
bar"'
|
|
|
|
f() {
|
|
echo `echo bar` && cat <<EOF
|
|
foo
|
|
EOF
|
|
}
|
|
check '"`f`" = "bar
|
|
foo"'
|
|
|
|
f() {
|
|
echo $(echo bar) && cat <<EOF
|
|
foo
|
|
EOF
|
|
}
|
|
check '"$(f)" = "bar
|
|
foo"'
|
|
|
|
exit $((failures != 0))
|