>
> This is known as dynamic scoping. There is text in the manual describing
> it.
>
Thank you, this was an interesting read. :)
Best,
On Mon, Jul 3, 2023 at 2:59 PM Chet Ramey wrote:
> On 7/2/23 9:04 AM, Top Dawn wrote:
> >>
> >> What makes you think so? Variables are always visible in invoked
On 7/2/23 9:04 AM, Top Dawn wrote:
What makes you think so? Variables are always visible in invoked
functions, unless you shadow them using local/declare/typeset.
Thank you very much for this information, I didn't know invoked functions
inherited their parent functions variables.
This is kn
On Sun, Jul 02, 2023 at 03:04:25PM +0200, Top Dawn wrote:
> >
> > What makes you think so? Variables are always visible in invoked
> > functions, unless you shadow them using local/declare/typeset.
> >
>
> Thank you very much for this information, I didn't know invoked functions
> inherited their
>
> What makes you think so? Variables are always visible in invoked
> functions, unless you shadow them using local/declare/typeset.
>
Thank you very much for this information, I didn't know invoked functions
inherited their parent functions variables.
I understand better now the use of declare -
On Sat, Jul 1, 2023, at 3:55 PM, Top Dawn wrote:
> I believe there is a bug with associative arrays, when once referenced in
> another function through the -n option, both the new reference name and the
> old one are made available.
>
> ```bash
>
> #!/bin/bash
> function my_function(){
> declar
Hello there,
I believe there is a bug with associative arrays, when once referenced in
another function through the -n option, both the new reference name and the
old one are made available.
```bash
#!/bin/bash
function my_function(){
declare -A my_array
my_array=(["one"]="one")
othe
