On 10/28/15 10:22 AM, Greg Wooledge wrote:
> Now, as for the changes from bash 4.2 to 4.3, I don't know the whole
> answer. Here are some of the changes from the CHANGES file:
>
> u. There are changes to the expansions peformed on compound array
> assignments,
> in an effort to make foo=(
On Wed, Oct 28, 2015 at 03:42:08PM +0100, Oskar Maier wrote:
> Furthermore, the original source is a small collection of bash
> function, purely for private use, hence I did not took too much pain to
> make it portable.
http://mywiki.wooledge.org/BashWeaknesses
#13 especially
Dear Greg,
thank you for the extensive reply, I've already learned something new.
The code I've posted was just intended as a minimal working example
without giving it to much thought, therefore please excuse the unquoted
"arr[@]". Furthermore, the original source is a small collection of bash
> On Wed, Oct 28, 2015 at 11:35:42AM +0100, Oskar Maier wrote:
> #!/bin/bash
>
> function printarray1 () {
> local -a arr=("${!1}")
> echo "${arr[@]}" # printing the complete array
> echo "${arr[9]}" # just to check if it is really recognized as an integer
> indexed array
> }
[...]
> print
On Wed, Oct 28, 2015 at 11:35:42AM +0100, Oskar Maier wrote:
> http://stackoverflow.com/questions/33371309/change-in-behaviour-of-declare-local-from-bash-4-2-to-4-3
Here is the text:
==
I've recently updated my system and got a new bash version. Since then I've
encoun
Hello,
I recently upgraded my Bash to 4.3 and soon after encountered a changed
behaviour in my Bash-scripts. Comment on my question posed at
Stackoverflow hint towards a bug. There I also explain the problem in
detail:
http://stackoverflow.com/questions/33371309/change-in-behaviour-of-declar
