On 5/7/14, 6:45 AM, Dan Douglas wrote:
> This might have the same fix. I guess Bash only checks for valid
> variable names during expansion or initial assignment.
Thanks, I already fixed this.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita
This might have the same fix. I guess Bash only checks for valid
variable names during expansion or initial assignment.
$ bash -xc 'typeset -n x; x=@ x=(ha ha); typeset -p @'
+ typeset -n x
+ x=@
+ x=(ha ha)
+ typeset -p @
declare -a @='([0]="ha" [1]="ha")'
Bash eventuall
On 4/27/14, 12:07 PM, Andre Holzhey wrote:
> Description:
> ${!Name:=Value} produces variables with illegal names. This does not
> directly disturb scripting, but it seems to open a terrible universe...
> Anyway, It would be nice, to make this combination work.
Thanks for the report.
ives '!Name=Value')
Fix:
[Description of how to fix the problem. If you don't know a
fix for the problem, don't include this section.]
From: andre.holz...@gmx.de
To: bug-bash@gnu.org,b...@packages.debian.org
Subject: Indirect parameter access combined w
