From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: new parameter expansion type?
Date: Tue, 31 Aug 1999 10:50:36 +0200 (MET DST) [thread overview]
Message-ID: <199908310850.KAA27246@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 30 Aug 1999 16:05:58 +0000
Bart Schaefer wrote:
> On Aug 30, 11:49am, Sven Wischnowsky wrote:
> } Subject: PATCH: new parameter expansion type?
> }
> } ${name^pattern^then^else}
> }
> } Gives you the (substituted) `then' string if the expansion of `name'
> } matches the `pattern' and otherwise it gives you the `else' string.
>
> Isn't this just the same as
>
> ${${${(M)name#pattern}:+then}:-else}
>
> except of course that you have to be a little selective about whether
> you use # or % to delimit the pattern?
Nice, hadn't thought about that.
> I'm not particularly excited by the ^test^true^false syntax nor by the
> trick of making "." magic in the true/false strings. I vote against this
> patch, in its current form at least. Sorry, Sven.
Especially with the thing above I have absolutely no problems with
that.
> } Ok, the `.' thingy is just because I couldn't think of a better
> } character/syntax (suggestions?) and this isn't as powerful as I would
> } like it because `then' and `else' can't expand to arrays. Maybe we
> } could make `${(A)foo^?^$arr1^$arr2}' do that (and maybe we could do
> } the same for `${(A)foo:-$arr}'.
>
> This is essentially the same problem as ${(A)foo:=string} where it would
> be nice to be able to have "string" be interpreted as an array. I pointed
> out the parsing problem with this back at that time. It would be nice to
> have a solution; Andrej suggested ${(A)foo:=(val1 val2 ...)} but it will
> require a change to the parser to make that work.
Or we could add a flag that says that the string is to be split into
different words and change `dquote_parse()' to allow us to say that
the `endchar' is any white-space (or any seperator character). I would
have suggested using the forms with a double character (as in
`${(A)arr:==a b c}') if that weren't too incompatible.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-08-31 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-31 8:50 Sven Wischnowsky [this message]
1999-08-31 17:47 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
1999-08-30 10:38 Sven Wischnowsky
1999-08-31 13:18 ` Andrej Borsenkow
1999-08-30 9:49 Sven Wischnowsky
1999-08-30 10:06 ` Andrej Borsenkow
1999-08-30 10:58 ` Tanaka Akira
1999-08-30 16:05 ` Bart Schaefer
1999-08-30 16:10 ` Peter Stephenson
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=199908310850.KAA27246@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).