[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-bash] Passing multiple arrays to a function
From: |
Chet Ramey |
Subject: |
Re: [Help-bash] Passing multiple arrays to a function |
Date: |
Thu, 14 Feb 2019 15:56:09 -0500 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 |
On 2/14/19 11:45 AM, Greg Wooledge wrote:
> On Thu, Feb 14, 2019 at 08:39:30AM -0500, Chet Ramey wrote:
>>> I have nothing good to say about that hack. At some point a couple
>>> years ago, we asked Chet whether it was actually a supported thing,
>>> or whether a future bug-fix of the parser might make it stop behaving
>>> this way, and the answer was inconclusive.
>>
>> I don't remember this discussion. Can you point me to a message or thread?
>
> The thread starts here:
> <https://lists.gnu.org/archive/html/bug-bash/2012-05/msg00138.html>
>
> Bill Gradwohl introduces the "hack" (my wording) here:
> <https://lists.gnu.org/archive/html/bug-bash/2012-05/msg00141.html>
>
> Your response is here:
> <https://lists.gnu.org/archive/html/bug-bash/2012-05/msg00152.html>
Well. In
https://lists.gnu.org/archive/html/bug-bash/2012-05/msg00152.html
I said that I would not change it unless I did something really dramatic
to the indirect expansion code. I implemented namerefs without changing
this feature -- nameref indirection works like ksh93 -- so I think we
can say it's there and changing it would be a break with backwards
compatibility.
I'll add something to the test suite so it can flag if something changes.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU address@hidden http://tiswww.cwru.edu/~chet/