Re: about the local not-on-every-function-separately var issue

2021-03-21 Thread Robert Elz
Date:Sun, 21 Mar 2021 22:42:19 -0400 From:Greg Wooledge Message-ID: | One or more of your assumptions are wrong. | | Bash uses "dynamic scope" when it expands variables. Note that some other shells don't really have local variables at all, there are only glob

Re: about the local not-on-every-function-separately var issue

2021-03-21 Thread Greg Wooledge
On Mon, Mar 22, 2021 at 03:12:25AM +0100, Alex fxmbsw7 Ratchev wrote: > i realize its somewhat of a big limitation, to have only global and > one level further ( local ) args, no per function One or more of your assumptions are wrong. Bash uses "dynamic scope" when it expands variables. This mea

about the local not-on-every-function-separately var issue

2021-03-21 Thread Alex fxmbsw7 Ratchev
i realize its somewhat of a big limitation, to have only global and one level further ( local ) args, no per function however about my code, i fixed it with a growing mapfile reader 'mapfile -t -d "" -O ${#big[@]} big <"$_hd"/init/"$per"' \ or at least partly fixed, yet stuff worked and eval t

is there no copy of vars declared for every function but one global 'local' only ?

2021-03-21 Thread Alex fxmbsw7 Ratchev
i have my codes much ready, but now on a clean reboot i noticed it doesnt do few stuffs anymore i call a per code that does eval, which i seem to call twice or trice inside stacked the content of args=( ) or files=( ) doesnt seem anymore active after some run could that be ? i guess the solution is