Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #16259

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

Show all headers | View raw

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 of shell functions and makes
>>   them context-dependent.
> 
> The purpose of 'readonly' as a variable attribute is to supplement a
> restricted shell environment.  If a variable is set readonly, it's because
> the system administrator, or whoever set up the enviroment, demands that
> this variable NOT be changed by the end user.

The second sentence is true, but extends beyond the restricted shell
environment. Variables are readonly for a reason.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Local variable names clash with global read-only variable names. Chet Ramey <chet.ramey@case.edu> - 2020-04-30 18:53 -0400

csiph-web