On Mon, Nov 23, 2020 at 05:20:22PM -0500, Greg Wooledge wrote:
> On Mon, Nov 23, 2020 at 07:36:29PM +, Jetzer, Bill wrote:
>...
> Exercises 1 and 2 apply directly...
>From man bash:
((expression))
The expression is evaluated according to the rules described be‐
On Wed, Nov 25, 2020 at 08:06:57AM +0700, Budi wrote:
> Can we validly write a line
>
> unset local a b c d e f g h i
>
> to mean: local a b c d e f g h i;unset a b c d e f g h i
No. And besides, you would want to unset *first*, right?
What are you actually trying to do here?
> if yes, how
LS,
Unless I have not read the manual properly, bash has an issue with the
key part used to address a value within associated arrays. I tried this
in the bash 4.4.x and 5.x series of bash under OpenSUSE 15.2 and TW.
Addressing associative arrays with an array statement - like echo
${k["${a[x
On Wed, Nov 25, 2020 at 02:48:44PM +0100, Frans de Boer wrote:
> Addressing associative arrays with an array statement - like echo
> ${k["${a[x]}"] does not work.
That seems to work for me, after I fix your quoting. Using your example
variables:
unicorn:~$ declare -A k
unicorn:~$ declare -a a
On 11/24/20 8:06 PM, Budi wrote:
> Can we validly write a line
>
> unset local a b c d e f g h i
>
> to mean: local a b c d e f g h i;unset a b c d e f g h i
No.
> if yes, how come local=9 is valid variable 'local' normally ? thanks much
Variables and builtin commands are in different namesp
