[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bash-3.2 Official Patch 20
From: |
Mike Frysinger |
Subject: |
Re: Bash-3.2 Official Patch 20 |
Date: |
Sat, 25 Aug 2007 22:48:04 -0400 |
User-agent: |
KMail/1.9.7 |
On Saturday 25 August 2007, Chet Ramey wrote:
> Mike Frysinger wrote:
> > 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 ...
>
> They're not readonly variables. The shell doesn't allow them to be unset,
> but you can assign new (even nonsense) values.
what i meant was that for some reason, i didnt get the readonly error after
modifying one of those four values, but the script stopped parsing at the
same spot since it was a readonly var ...
(UID=1)
-bash: UID: readonly variable
(BASH_ARGV=""; UID=1; echo HI)
<no error about UID being readonly, no echo "HI">
-mike
signature.asc
Description: This is a digitally signed message part.