Hello all, I have found a problem with the declare builtin.
Patch Level: 33 Release Status: release Description: Apparently, there is a problem with how bash interprets some variable assignments. It only happens in a function (probably related to `declare' making variables local). Repeat-By: # OK $ x() { declare -a var=(); declare -p var; }; x declare -a var='()' # not OK $ y() { declare -a var='()'; declare -p var; }; y bash: declare: var: not found Note that the format used in y is what `declare -p' displays. By the way, empty arrays seem to be reported as "not set". a=(); test -v a || echo "not set" This might be related (or not), but consider that the return status of `test -v' is different on a bash version unaffected by the bug that I have tried (4.2.37).