<sorry if this comes thru' twice> Chet Ramey wrote:
> There is a difference in behavior between bash-3.0 and bash-3.1 involving > parsing of single- and double-quoted strings occurring in old-style > command substitution. The difference has to do with how backslashes are > processed. This patch restores a measure of backwards compatibility while > the question of POSIX conformance and ultimately correct behavior is > discussed. Hi, It appears there might be problem with this patch. Here is a test case I distilled from the grep-2.5.1a testsuite: status=`echo '-'| { ${GREP} -E -e 'a\' >/dev/null 2>&1 ; echo $?; }` Put that line into a file called "myfile" then run like this: # bash -n myfile myfile: line 1: unexpected EOF while looking for matching `'' myfile: line 2: syntax error: unexpected end of file AFAICT, this used to be accepted by older Bash versions. Do you think problem lies with this Bash patch or with test case? Thanks Greg -- http://www.diy-linux.org/ _______________________________________________ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash