Re: Is this the expected behaviour for nameref in Bash 4.4 now?
From:
Dan Douglas
Subject:
Re: Is this the expected behaviour for nameref in Bash 4.4 now?
Date:
Thu, 20 Oct 2016 15:02:48 -0500
Yes that was an intentional change to require valid identifiers. I can't
say it will always be that way or that there won't at some point be a
workaround. You can stiill use `${!param}' for now to refer to positional
parameters as you always could, but as usual that isn't useful if you
want to assign by reference.