From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: zsh-workers@zsh.org
Subject: Re: [PATCH 1/3] Extended ksh compatibility: namespace parameter syntax
Date: Sat, 20 May 2023 13:32:23 -0400 [thread overview]
Message-ID: <ZGkEJ5ue3SJnbQ3f@fullerene.field.pennock-tech.net> (raw)
In-Reply-To: <CAH+w=7bjStThTiTpEgem636Hr3Uev9CjLMUBhR1OWGNOvsfq4Q@mail.gmail.com>
On 2023-05-19 at 23:54 -0700, Bart Schaefer wrote:
> On Fri, May 19, 2023 at 7:06 PM Phil Pennock
> <zsh-workers+phil.pennock@spodhuis.org> wrote:
> > AFAICT, in zsh, .a.b=c is assigning to var b in namespace a, while a.b=c
> > is setting the b attribute of the compound variable a.
>
> As presently implemented, there's no difference. The latter is
> supported by the parser but should be considered a reserved syntax;
> some sort of compound variable feature is a possible future
> application.
Sorry, I thought I'd fixed that typo before sending.
In _ksh_.
I played with ksh to evaluate the behavior, which didn't match what was
said upthread, which is why I spoke up to clarify the distinction.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~8< ksh >8~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
% ksh
$ echo ${.sh.version}
Version AJM 93u+ 2012-08-01
$ PS1='ksh$ '
ksh$ foo=( alpha=first beta=second ) # compound var
ksh$ namespace bar { alpha=one beta=two ; }
ksh$ echo ${foo}
( alpha=first beta=second )
ksh$ echo ${.foo}
ksh$ echo ${bar}
ksh$ echo ${.bar}
alpha beta
ksh$ foo.gamma=third
ksh$ echo $foo
( alpha=first beta=second gamma=third )
ksh$ .bar.gamma=three
ksh$ echo ${.bar}
alpha beta
ksh$ namespace bar { echo $gamma; }
three
ksh$ echo ${.bar.gamma}
three
ksh$ echo ${@foo}
typeset -C
ksh$ echo ${@bar}
ksh$ echo ${@.bar}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~8< ksh >8~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I don't know what's going on with `echo ${.bar}`, it's undocumented in
my man-page and the inability to use ${@vname} to get details about it
suggests perhaps it shouldn't expand?
( ksh ${@vname} ~~ zsh ${(t)vname} )
So, to match the intent of ksh as I understand it:
* .identifier.x is always treating identifier as a namespace
* identifier.x is always treating identifier as a compound var
* this is consistent across assignment LHS and expansion
-Phil
next prev parent reply other threads:[~2023-05-20 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 3:56 Bart Schaefer
2023-03-05 9:10 ` Oliver Kiddle
2023-03-05 9:57 ` Sebastian Gniazdowski
2023-03-05 20:20 ` Bart Schaefer
2023-03-05 21:11 ` Bart Schaefer
2023-03-05 20:16 ` Bart Schaefer
2023-03-05 22:24 ` Oliver Kiddle
2023-03-05 22:42 ` Bart Schaefer
2023-05-20 2:05 ` Phil Pennock
2023-05-20 6:54 ` Bart Schaefer
2023-05-20 17:32 ` Phil Pennock [this message]
2023-05-22 2:36 ` Mikael Magnusson
2023-05-22 4:35 ` Bart Schaefer
2023-05-22 21:02 ` Phil Pennock
2023-05-24 15:57 ` Oliver Kiddle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZGkEJ5ue3SJnbQ3f@fullerene.field.pennock-tech.net \
--to=zsh-workers+phil.pennock@spodhuis.org \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).