helpThe GNU Bourne-Again SHell - Support: sr #107871, associative array assignment is...


sr #107871: associative array assignment is more constrained when using () construct, than when using direct [] assignment

Submitted by:  Michal Soltys <msoltyspl>
Submitted on:  Mon 14 Nov 2011 04:06:08 PM UTC  
Category: NonePriority: 5 - Normal
Severity: 3 - NormalStatus: Done
Privacy: PublicAssigned to: None
Open/Closed: OpenOperating System: GNU/Linux

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Wed 25 Mar 2015 03:05:28 PM UTC, comment #1:

Fixed, close.

dualbus@yaqui:~$ declare -A foo
dualbus@yaqui:~$ foo=(['ab]']=bar )
dualbus@yaqui:~$ declare -p foo
declare -A foo='(["ab]"]="bar" )'

Eduardo Bustamante <dualbus>
Mon 14 Nov 2011 04:06:08 PM UTC, original submission:

For example:

declare -A foo

will work perfectly fine, but:

foo=( ['ab]']=bar )

will end with following error:

-bash: [ab]]=bar: bad array subscript

Michal Soltys <msoltyspl>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by chet (Updated the item)
  • -unavailable- added by dualbus (Posted a comment)
  • -unavailable- added by msoltyspl (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follows 1 latest change.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 12 Nov 2015 11:37:13 PM UTCchetStatusNone=>Done

    Back to the top

    Powered by Savane 3.1-cleanup1