Re: How functions are defined

2020-04-28 Thread Andreas Schwab
On Apr 27 2020, 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 simple co

Re: How functions are defined

2020-04-28 Thread Robert Elz
Date:Mon, 27 Apr 2020 22:03:47 -0400 From:wor...@alum.mit.edu (Dale R. Worley) Message-ID: <87pnbsfjss@hobgoblin.ariadne.com> | While I was looking at the details of parsing function definitions, I | tripped on something I should have noticed long ago. In the

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

2020-04-28 Thread andrej--- via Bug reports for the GNU Bourne Again SHell
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin' -DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/ba

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

2020-04-28 Thread Greg Wooledge
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 of shell functions and makes > them context-de