Date: Fri, 13 Mar 2009 06:24:03 +0200 From: Eray Aslan <eray.aslan@caf.com.tr> To: freebsd-questions@freebsd.org Subject: Re: Problem with Bash-4 and $(command) syntax Message-ID: <49B9DFE3.9000409@caf.com.tr> In-Reply-To: <49B9409A.29090.10C8FB5@markmcconnell.iinet.com> References: <20090312102523.6f5ad248@scorpio> <49B9409A.29090.10C8FB5@markmcconnell.iinet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13.03.2009 02:04, Mark McConnell wrote:
> On 12 Mar 2009 at 10:25, Jerry wrote:
> {Problem with Bash-4 and $(command) ...}:
[...]
> I found the same problem, and have reverted to
> bash3.2 until it's sorted out.
See if the following helps.
http://tiswww.case.edu/php/chet/bash/COMPAT
Especially:
38. Since bash-4.0 now follows Posix rules for finding the closing
delimiter of a $() command substitution, it will not behave as previous
versions did, but will catch more syntax and parsing errors before
spawning a subshell to evaluate the command substitution.
--
Eray
> Like you, I wasn't able to find discussion of this on
> the lists I subscribe to - although I'm sure it's going
> on. Looking through the diffs in
> /usr/ports/distfiles/bash, the bracketed form of
> command substitution appears to be a long-
> standing problem in bash40-xxx.
>
> The back-tick `command` form works as it should,
> but not the Posix-style $(command) form, as of
> GNU bash, version 4.0.10(1)-release
>
> Mark
> --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49B9DFE3.9000409>