From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: new parameter expansion type?
Date: Tue, 31 Aug 1999 17:18:21 +0400 [thread overview]
Message-ID: <000001bef3b3$4c738fd0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <199908301038.MAA20917@beta.informatik.hu-berlin.de>
> >
> > Remember discussion of backreference in new regexp implementation?
> I think, we
> > should unify it with ${.../...} & Co code. There are two possibilities:
>
> Sure I remember that, but it's a different thing -- or how would you
> do an if-then-else with `${.../...}'? Or are you suggesting
> `${.../pat/repl-then/repl-else}'? Hm.
>
No. What I suggest is
1. enable use of subpatterns
2. save the results of last pattern match in defined variables, e.g. $MATCH
(scalar) for a whole match and $match (array) for subpatterns. Yes, it has som
eimpact, but e.g. in case of $foo == bar MATCH is reduntant (we match the whole
string anyway) and we can use option to turn it off.
3. now these variables can be used in ${.../...} and in ${...^...} in
replacement part. So, you can write
${foo^$~bar^$baz^$MATCH}.
Or
${foo/\([[:alpha:]]##\)\([[:letter:]]\)/$match[1]:$match[2]}
4. And these variables can be also used outside of expansion:
case $foo in
any_pattern)
print $match[3]
/andrej
next prev parent reply other threads:[~1999-08-31 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 10:38 Sven Wischnowsky
1999-08-31 13:18 ` Andrej Borsenkow [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-08-31 8:50 Sven Wischnowsky
1999-08-31 17:47 ` Bart Schaefer
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='000001bef3b3$4c738fd0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=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).