[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bash-3.1 Official patch 10
From: |
Greg Schafer |
Subject: |
Re: Bash-3.1 Official patch 10 |
Date: |
Wed, 22 Feb 2006 14:20:10 +1100 |
User-agent: |
Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) |
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 think problem lies with this Bash patch or with test case?
Thanks
Greg
--
http://www.diy-linux.org/