Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: [PATCH 1/3] Extended ksh compatibility: namespace parameter syntax

X-seq: zsh-workers 51505
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
Cc: Zsh hackers list <zsh-workers@xxxxxxx>
Subject: Re: [PATCH 1/3] Extended ksh compatibility: namespace parameter syntax
Date: Sun, 5 Mar 2023 12:20:56 -0800
Archived-at: <https://zsh.org/workers/51505>
In-reply-to: <CAKc7PVB=cbu6OBN7GMB31SNzXsMO4V5E+rQifJpg4uvZtUU=WA@mail.gmail.com>
List-id: <zsh-workers.zsh.org>
References: <CAH+w=7aV2s_+79eCPuavRTiR5wRTwDtTjYxP_VN8HNtL2R5iXw@mail.gmail.com> <26170-1678007435.186071@mDq6.Euc0.bAwZ> <CAKc7PVB=cbu6OBN7GMB31SNzXsMO4V5E+rQifJpg4uvZtUU=WA@mail.gmail.com>

On Sun, Mar 5, 2023 at 1:57 AM Sebastian Gniazdowski
<sgniazdowski@xxxxxxxxx> wrote:
>
> I wonder, how far is this from supporting a nested arrays? Like arr[2][3] or assoc[a][c]?

It's exactly as far as it has always been.  Zsh's internal
implementation of indexed arrays does not support
pointers-to-pointers, and associative arrays have always had most of
the plumbing for that but not what might be called the contextual
clues.  None of what's in these patches gets any closer to refactoring
for either case.

Follow-Ups:
- Re: [PATCH 1/3] Extended ksh compatibility: namespace parameter syntax
  - From: Bart Schaefer

References:
- [PATCH 1/3] Extended ksh compatibility: namespace parameter syntax
  - From: Bart Schaefer
- Re: [PATCH 1/3] Extended ksh compatibility: namespace parameter syntax
  - From: Oliver Kiddle
- Re: [PATCH 1/3] Extended ksh compatibility: namespace parameter syntax
  - From: Sebastian Gniazdowski

Messages sorted by: Reverse Date, Date, Thread, Author