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: Mon, 22 May 2023 17:02:11 -0400 [thread overview]
Message-ID: <ZGvYU//xw/ZLjWOK@fullerene.field.pennock-tech.net> (raw)
In-Reply-To: <CAH+w=7a8Um9QJK_QnkMEKnAxcKJOce_cfDXFfKmTnNo5V56d5g@mail.gmail.com>
On 2023-05-21 at 21:35 -0700, Bart Schaefer wrote:
> On Sun, May 21, 2023 at 7:36 PM Mikael Magnusson <mikachu@gmail.com> wrote:
> > > 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
> >
> > Does this mean compound vars can't be namespaced?
>
> No, but it does mean namespaces can't be nested.
Bart is (as per 99.9% of the time) correct. The examples below might
make it clearer (and are original to me so fine to grab into the test
suite). Note though that ksh does have nested collection types, which
would make full zsh compatibility trickier:
Attributes assigned by the typeset special built-in command ap‐
ply to all elements of the array. An array element can be a
simple variable, a compound variable or an array variable. An
element of an indexed array can be either an indexed array or
an associative array. An element of an associative array can
also be either. To refer to an array element that is part of
an array element, concatenate the subscript in brackets. For
example, to refer to the foobar element of an associative array
that is defined as the third element of the indexed array, use
${vname[3][foobar]}
$ namespace foo { bar=(alpha=one beta=two gamma=three); }
$ echo ${.foo.bar.alpha}
one
$
$ namespace first { namespace second { item=42; } }
$ echo ${.second.item}
42
$ echo ${.first.second.item}
$ typeset -p
[ ... skipping much before/after/between these ... ]
namespace first
{
:
}
namespace foo
{
typeset -C bar=()
}
namespace second
{
item=42
}
$ namespace a { b=( c=(one two three) d=([ichi]=1 [ni]=2 [san]=3) ); }
$ echo ${.a.b.c[@]}
one two three
$ echo ${!.a.b.d[@]}
ichi ni san
$ echo ${.a.b.d[@]}
1 2 3
$ echo ${.a.b.d[ni]}
2
$
-Phil
next prev parent reply other threads:[~2023-05-22 21:02 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
2023-05-22 2:36 ` Mikael Magnusson
2023-05-22 4:35 ` Bart Schaefer
2023-05-22 21:02 ` Phil Pennock [this message]
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=ZGvYU//xw/ZLjWOK@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).