Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: namespaces limitation
- X-seq: zsh-workers 51793
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Oliver Kiddle <opk@xxxxxxx>
- Cc: Zsh workers <zsh-workers@xxxxxxx>
- Subject: Re: namespaces limitation
- Date: Thu, 25 May 2023 16:13:14 -0700
- Archived-at: <https://zsh.org/workers/51793>
- In-reply-to: <CAH+w=7YBoMrNOokZmDJJehv2oF_RUkhY=USmJFHb-A8X32LaLA@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- References: <9849-1684455235.063540@_q24.9gsR.Efjj> <CAH+w=7ZZRQiboQYwgnZwpkger+i2pnyP3Y55gC4vnwkVnfUJCg@mail.gmail.com> <92928-1684946470.047218@Qy70.4SHd.nnDI> <CAH+w=7YBoMrNOokZmDJJehv2oF_RUkhY=USmJFHb-A8X32LaLA@mail.gmail.com>
On Thu, May 25, 2023 at 3:09 PM Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
>
> I still haven't worked out how to deal correctly with .var.3x -- ksh
> allows .var.3 but rejects .var.3x
Also, paramsubst() doesn't apply the same rules in the same way as
assignments, so getting both .var.3x=y and ${.var.3x} to be rejected
is annoyingly complex.
Even rejecting .var.3x=y in zsh produces "not an identifier" whereas
ksh attempts to run a command of that name ... that may not be worth
tackling.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author