From: Geoff Wing <mason@primenet.com.au>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@math.gatech.edu
Subject: Re: RC_EXPAND_PARAM bug
Date: Wed, 30 Jul 1997 13:04:11 +1000 [thread overview]
Message-ID: <19970730130411.45672@primenet.com.au> (raw)
In-Reply-To: <970729092705.ZM16897@candle.brasslantern.com>; from Bart Schaefer on Tue, Jul 29, 1997 at 09:27:05AM -0700
Bart Schaefer wrote about Re: RC_EXPAND_PARAM bug:
:On Jul 29, 7:47am, Geoff Wing wrote:
:} :The logic is that the string after the rc-param, 1${^^x}, is expanded,
:} :producing two strings, 1x y, which is combined with 1a 1b. It is true
:} I don't get this, shouldn't 1${^^x} produce one string "1x y"? And then the
:} expansion of 1${^a}1${^^x} be the string "1a1x y 1b1x y"? Your logic
:} indicates to me that it's producing array like thingies. Is this dependant
:} on some other wierd option? Please explain before I go mental.
:The trick there is that x is an array variable, so it produces two strings.
Yes, but I still don't get it. ^^ should prevent expansion, shouldn't it.
${^spec}
Turn on the RC_EXPAND_PARAM option for the evaluation of spec;
if the ^ is doubled, turn it off. When this option is set, array
expansions of the form foo${xx}bar, where the parameter xx is set
to (a b c), are substituted with fooabar foobbar foocbar
instead of the default fooa b cbar.
So, it seems to me that it should be
% echo 1${^a}
1a 1b
% echo 1${^a}1
1a1 1b1
% echo 1${^a}1${^x}
1a1x 1a1y 1b1x 1b1y # in another order?
% echo 1${^a}1${^^x}
1a1x y 1b1x y
--
Geoff Wing [mason@primenet.com.au] Phone : +61-3-9818 2977
Technical Manager: PrimeNet Computer Consultants Facsimile: +61-3-9819 3788
Web: <URL:http://www.primenet.com.au/> Mobile : 0412 162 441
[ Boulderdash: <URL:http://ciips.ee.uwa.edu.au/~williams/bd/> ]
next prev parent reply other threads:[~1997-07-30 3:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-28 13:42 Andrew Main
1997-07-28 16:26 ` Bart Schaefer
1997-07-29 6:04 ` Zoltan Hidvegi
1997-07-29 7:09 ` Bart Schaefer
1997-07-29 7:36 ` Zoltan Hidvegi
1997-07-29 7:47 ` Geoff Wing
1997-07-29 16:27 ` Bart Schaefer
1997-07-30 3:04 ` Geoff Wing [this message]
1997-07-30 3:56 ` Bart Schaefer
1997-07-30 5:16 ` Zoltan Hidvegi
1997-07-30 5:46 ` Andrej Borsenkow
1997-07-30 6:11 ` Bart Schaefer
1997-07-30 6:51 ` Zoltan Hidvegi
1997-07-30 7:33 ` Bart Schaefer
1997-07-30 8:18 ` Andrew Main
1997-07-30 15:54 ` Andrej Borsenkow
1997-07-30 17:05 ` Bart Schaefer
1997-08-01 13:17 ` Andrej Borsenkow
1997-08-01 18:18 ` 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=19970730130411.45672@primenet.com.au \
--to=mason@primenet.com.au \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@math.gatech.edu \
/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).