[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: indirect variable behavior breakage
|
From: |
Greg Wooledge |
|
Subject: |
Re: indirect variable behavior breakage |
|
Date: |
Wed, 7 Mar 2018 11:09:10 -0500 |
|
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Wed, Mar 07, 2018 at 10:54:22AM -0500, christopher barry wrote:
> So yes 'ivar -3' is very, very bad indeed, and was a nasty bug, and I
> absolutely agree that making sure the string is a validly formatted var
> name before attempting to evaluate it is the right approach.
>
> My only request is for bash to not throw an error when it realizes
> it's invalid. Returning 1 and no data seems like a reasonable response
> that fixes the prior bug, but will not break this use-case.
Just out of curiosity, what *is* this use case, and why are you not
using an associative array?
It seems like you are trying to map strings of gibberish to nothing, and
strings of non-gibberish to values. An associative array does that.