On Saturday 25 August 2007, Chet Ramey wrote: > Mike Frysinger wrote: > >> Bug-Description: > >>> In some cases of error processing, a jump back to the top-level > >>> processing loop from a builtin command would leave the shell in an > >>> inconsistent state. > >> > >> this appears to break handling of read only variables in source > >> statements > > > > this may also just be a bug fix, i just want confirmation before we go > > changing things :) > > I've considered it, and concluded that the post-patch 20 behavior is the > right thing. If a variable assignment error occurs during execution of > a builtin, it should cause the builtin to return with a non-failure status > (unless you're running a non-interactive shell in posix mode, in which > case Posix says the whole shell should exit). > > I do see what Gentoo is trying to do, and I'll try to devise a workaround > to accommodate both needs.
thanks
a side note ... if you change any of BASH_{ARGC,ARGV,LINENO,SOURCE} before
setting a readonly variable, bash will not spit out the error message about
the variable being readonly ...
(UID=1)
-bash: UID: readonly variable
(BASH_ARGC= UID=1)
<no output>
this regression seems to have appeared between the last bash-2 and the first
bash-3 ...
-mike
signature.asc
Description: This is a digitally signed message part.
