zsh-users
 help / color / mirror / code / Atom feed
From: "S. Cowles" <scowles@earthlink.net>
To: zsh users <zsh-users@sunsite.dk>
Subject: Re: help with dereferencing variables
Date: Sat, 14 Feb 2004 20:12:32 -0800	[thread overview]
Message-ID: <200402142012.51392.scowles@earthlink.net> (raw)
In-Reply-To: <1040214212400.ZM15293@candle.brasslantern.com>


Many thanks; that was the info I was missing.  One small aesthetics preference 
following up on your suggestion and I'm away (does not preserve newlines in 
the array element assignments):

eval ${key}\=\( ${(P)val} \)

cheers.


On Saturday 14 February 2004 13:24, Bart Schaefer wrote:
> On Feb 14,  9:59am, S. Cowles wrote:
> }
> } In the following code, method 1 gives the expected results. Method
> } 2, however, breaks with the error: unknown file attribute. Is the
> } eval in Method 1 required, or is there a correct syntax to make the
> } dereference occur in Method 2 without an eval?
>
> The short answers are "not precisely" and "no".
>
> } 	# method 1:
> } 	b=$(echo "${key}=( ${(@)${(P)val}} )")
> } 	eval $b
>
> You don't need the $(echo) and the assignment to $b here.  It should be
> enough to do
>
> 	eval ${key}'=( ${(P)val} )'
>
> (note placement of single quotes).
>
> } 	# method 2:
> } 	${key}=( ${(@)${(P)${val}}} )
>
> This syntax is not an assignment, because the stuff to the left of the
> equals sign is not an identifier name.  (This used to work in older
> versions of zsh because the variable was expanded before zsh looked
> for assignment syntax, but that was incompatible with other shells.)
>
> Even if this were an assignment, The ${(@)...} is extraneous when the
> whole thing is not in double quotes.  And you don't need ${(P)${val}},
> just ${(P)val} is enough.




  reply	other threads:[~2004-02-15  4:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14 17:59 S. Cowles
2004-02-14 21:24 ` Bart Schaefer
2004-02-15  4:12   ` S. Cowles [this message]
2004-02-15 17:04     ` Bart Schaefer

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=200402142012.51392.scowles@earthlink.net \
    --to=scowles@earthlink.net \
    --cc=zsh-users@sunsite.dk \
    /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).