Re: Local variable names clash with global read-only variable names.

2020-04-30 Thread Dale R. Worley
>>> f() { local x=a; } >>> declare -r x >>> f # bash: local: x: readonly variable >>> >>> This^^^ should not fail; it hinders reusability of shell functions and >>> makes >>> them context-dependent. It's "natural" to think that a variable that is local to a function should be ind

Re: Local variable names clash with global read-only variable names.

2020-04-30 Thread Chet Ramey
On 4/28/20 2:28 PM, Greg Wooledge wrote: > On Tue, Apr 28, 2020 at 08:14:28PM +0200, andrej--- via Bug reports for the > GNU Bourne Again SHell wrote: >> f() { local x=a; } >> declare -r x >> f # bash: local: x: readonly variable >> >> This^^^ should not fail; it hinders reusability

Re: How functions are defined

2020-04-30 Thread Chet Ramey
On 4/27/20 10:03 PM, Dale R. Worley wrote: > So it seems the reserved rule is more accurately: > >Reserved words are words that have a special meaning to the >shell. The following words are recognized as reserved when >unquoted and either (1) where the first word of a sim

Potential restricted bash escape by modifying history file

2020-04-30 Thread Diffie
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr