From: Danek Duvall <duvall@emufarm.org>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: 4.1: multi-parameter for loop
Date: Wed, 20 Jun 2001 15:56:22 -0700 [thread overview]
Message-ID: <20010620155622.A3447@lorien.emufarm.org> (raw)
In-Reply-To: <Tc0a88d015443e66af4@mailsweeper01.cambridgesiliconradio.com>; from pws@csr.com on Wed, Jun 20, 2001 at 08:12:09PM +0100
On Wed, Jun 20, 2001 at 08:12:09PM +0100, Peter Stephenson wrote:
> "Bart Schaefer" wrote:
> > Well, there's this:
> >
> > for in in in in; do echo $in; done
>
> It will stop reading parameters when it reaches the second `in'. I meant
> to document this, although it should be pretty obvious.
Right. That lacks ambiguity because multiple distinct parameters can't
have the same name. But that ambiguity is missing in
for i in in in; do ....
Do you set $i to "in" and "in" or do you set $i and $in set to "in" and ""?
Posix presumably would simply use the first interpretation, and if you want
something like the second, just don't use a parameter named in? Or am I
missing the disambiguation?
Danek
next prev parent reply other threads:[~2001-06-20 22:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 14:45 Peter Stephenson
2001-06-20 16:11 ` Peter Stephenson
2001-06-20 18:01 ` Andrej Borsenkow
2001-06-20 18:20 ` Bart Schaefer
2001-06-20 18:39 ` Peter Stephenson
2001-06-20 18:55 ` Bart Schaefer
2001-06-20 19:12 ` Peter Stephenson
2001-06-20 22:56 ` Danek Duvall [this message]
2001-06-21 7:19 ` Andrej Borsenkow
2001-06-21 9:52 ` Peter Stephenson
2001-06-21 10:34 ` PATCH (redux): POSIX `for' syntax Bart Schaefer
2001-06-21 15:31 ` PATCH (redux): non-POSIX " Peter Stephenson
2001-06-25 16:05 ` Peter Stephenson
2001-06-21 9:55 ` PATCH: POSIX " Bart Schaefer
2001-06-22 6:29 ` PATCH: test case for " Andrej Borsenkow
2001-06-22 23:49 ` PATCH: 4.1: multi-parameter for loop Zefram
2001-06-23 0:04 ` Bart Schaefer
2001-06-21 8:33 ` Sven Wischnowsky
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=20010620155622.A3447@lorien.emufarm.org \
--to=duvall@emufarm.org \
--cc=zsh-workers@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).