[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Variable with the same name can't be declared in the local scope if the

From: 林博仁Buo-ren , Lin
Subject: Variable with the same name can't be declared in the local scope if the global one is declared read-only
Date: Sun, 15 Nov 2020 17:20:14 +0800

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
-fstack-protector-strong -Wformat -Werror=format-security -Wall
heses -Wno-format-security
uname output: Linux brlin-musicha-mz-530 5.4.0-52-generic #57-Ubuntu
SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 5.0
Patch Level: 17
Release Status: release

       Example script reproducing the bug:

       #!/usr/bin/env bash
       # Depict the variable shadowing phenomenon
       # ./depict-the-variable-shadowing-phenomenon.bash
       set \
           -o errexit \
           -o errtrace \
           -o nounset

       declare -r variable_shadowed='(Value to be shadowed in the function)'

           local -r variable_shadowed="Another value"

           printf 'In the %s context: \n' "${FUNCNAME[0]}"
           printf 'variable_shadowed = %s\n' "${variable_shadowed}"

       ## Expected behavior

       $ ./depict-the-variable-shadowing-phenomenon.bash
       In the check_values_of_variables_in_different_scope context:
       variable_shadowed = Another value

       ## Current behavior

       $ LANG=C ./depict-the-variable-shadowing-phenomenon.bash
       ./depict-the-variable-shadowing-phenomenon.bash: line 11:
local: variable_shadowed: readonly variable

       Refer the "Descripton" section.

       I suggest that bash shouldn't trigger the error, if the
variable to be set is a `different` variable
       instantiated by the variable shadowing mechanism.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]