From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Typeset with array
Date: Wed, 24 Jun 2015 08:03:48 -0700 [thread overview]
Message-ID: <150624080348.ZM18711@torch.brasslantern.com> (raw)
In-Reply-To: <20150624101404.71c21adc@pwslap01u.europe.root.pri>
On Jun 24, 10:14am, Peter Stephenson wrote:
}
} > This has me trying to think of ways to implement the ksh ([key]=value)
} > syntax.
} >
} > typeset -a varname=([k1]=v1 [k2]=v2)
Incidentally, I just stumbled over the bash feature that you can set
elements of a regular array this way as well.
bash$ array=([0]="a" [2]="b" [1]="")
bash$ typeset -p array
declare -a array='([0]="a" [1]="" [2]="b")'
bash$
I believe someone else already pointed out that looking inside the quoted
value for a parenthesized list has its own set of problems.
Ksh always creates an associative array with that syntax unless explictly
told otherwise, but it accepts it for normal arrays:
ksh$ array=([0]="a" [2]="b" [1]="")
ksh$ typeset -p array
typeset -A array=([0]=a [1]='' [2]=b)
ksh$ typeset -a array=([0]="a" [2]="b" [1]="")
ksh$ typeset -p array
typeset -a array=(a '' b)
ksh$
So it really is just the same as mapping the variable name across the
values in the list.
} However, You could get away with detecting the form until the list is
"not detecting"?
} expanded: that's now in two different places, addvars and execcmd, but
} could easily be made common --- put something in front of the
} ecgetlist() that retrieves the array. As long as you detect it before
} attempting to glob, to avoid NO_MATCH behaviour, it ought to work. This
} is easier as there are no wordcode changes and I can't see any obvious
} gotchas. I'm not sure what expansions apply: do k* get expanded at all?
} Presumably v* get single word expansion?
ksh$ echo D*
Doc
ksh$ typeset array=([D*]=D*)
ksh$ typeset -p array
typeset -A array=(['D*']='D*')
ksh$
But note:
ksh$ typeset -A array=([*]=*)
ksh: *: invalid subscript in assignment
ksh$
prev parent reply other threads:[~2015-06-24 15:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5578996E.3080700@thequod.de>
[not found] ` <150610191427.ZM30841@torch.brasslantern.com>
[not found] ` <5579C247.1060800@thequod.de>
[not found] ` <150611183639.ZM32247@torch.brasslantern.com>
[not found] ` <20150612094237.338f79d5@pwslap01u.europe.root.pri>
2015-06-19 11:39 ` Peter Stephenson
2015-06-19 14:06 ` Peter Stephenson
2015-06-19 18:54 ` Bart Schaefer
2015-06-19 20:16 ` Peter Stephenson
2015-06-19 21:11 ` Eric Cook
2015-06-19 16:09 ` Bart Schaefer
2015-06-19 20:32 ` Peter Stephenson
2015-06-20 3:50 ` Bart Schaefer
2015-06-20 17:05 ` Peter Stephenson
2015-06-19 17:36 ` Oliver Kiddle
2015-06-19 18:40 ` Bart Schaefer
2015-06-25 9:29 ` Peter Stephenson
2015-06-25 15:16 ` Bart Schaefer
2015-06-25 15:39 ` Peter Stephenson
2015-06-25 16:08 ` Bart Schaefer
2015-06-25 16:34 ` Peter Stephenson
2015-06-26 13:51 ` PATCH: array slice Peter Stephenson
2015-06-26 23:07 ` Bart Schaefer
2015-06-27 19:42 ` Peter Stephenson
2015-06-27 20:09 ` Bart Schaefer
2015-06-26 16:46 ` PATCH: typeset completion Peter Stephenson
2015-06-26 19:14 ` Typeset with array Oliver Kiddle
2015-06-27 16:33 ` Peter Stephenson
2015-06-21 20:05 ` Peter Stephenson
2015-06-21 20:38 ` Peter Stephenson
2015-06-23 16:47 ` Peter Stephenson
2015-06-23 17:52 ` Mikael Magnusson
2015-06-23 20:17 ` Bart Schaefer
2015-06-23 20:21 ` Peter Stephenson
2015-06-23 20:24 ` Mikael Magnusson
2015-06-24 1:35 ` typeset -p with assoc array (was Re: Typeset with array) Bart Schaefer
2015-06-24 6:03 ` Bart Schaefer
2015-06-23 20:25 ` Typeset with array Bart Schaefer
2015-06-24 9:14 ` Peter Stephenson
2015-06-24 9:29 ` Peter Stephenson
2015-06-24 10:35 ` Roman Neuhauser
2015-06-24 13:00 ` Mikael Magnusson
2015-06-24 13:20 ` Peter Stephenson
2015-06-24 15:03 ` Bart Schaefer [this message]
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=150624080348.ZM18711@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).