On 1/15/13 11:30 AM, DJ Mills wrote:
> I believe that's referring to var=value command, as in the syntax to export
> a variable into "command"s environment.
>
> readonly a=3
> a=2 echo foo
I believe this is the bug:
set -o posix
readonly a=0
a=1 command : 2>/dev/null # or use true in place of command :
readonly b=0
echo after
bash-4.1 exited without getting to the `echo after', which is clearly
wrong. The original version came from FreeBSD's sh regression test suite.
I thought the change in bash-4.2 fixed the problem, but I now think
another change masked the problem without fixing it. (Try it, it's still
broken in bash-4.2.)
I've fixed the problem and the fix will be in the next release.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
