zsh-workers
 help / color / mirror / code / Atom feed
From: Philippe Troin <phil@fifi.org>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: For loop bug
Date: 15 Sep 2002 21:58:33 -0700	[thread overview]
Message-ID: <87elbufs3q.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <1020914045657.ZM12939@candle.brasslantern.com>

"Bart Schaefer" <schaefer@brasslantern.com> writes:

> On Sep 13,  5:58pm, Philippe Troin wrote:
> } Subject: Re: For loop bug
> }
> } Peter Stephenson <pws@pwstephenson.fsnet.co.uk> writes:
> } 
> } Does it fix this one as well?
> } 
> }   % for i in 1 2 3; do { {echo $i; [[ $i == 2 ]] && exit 1; } || break }; \
> }   > done && echo X
> }   1
> }   X
> }   % 
> 
> That is not a bug.
> 
> zagzig% [[ x == y ]] && true
> zagzig% echo $?
> 1
> 
> Hence { [[ $i == 2 ]] && exit 1; } is false, and { false || break } means
> break.  The && expression is only true if -both- branches are true.

Agreed.

> Further, { } is not a subshell, so { [[ 2 == 2 ]] && exit 1; } would most
> likely produce something like
> 
> login:
> 
> which might surprise you even more.

I'm not sure I get this part.

But shouldn't it print:

  1
  2
  X

???

The echo $i with i set to 2 occurs before the exit and break
statements.

Phil.


  reply	other threads:[~2002-09-16  4:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13 18:25 Philippe Troin
2002-09-13 23:31 ` Peter Stephenson
2002-09-14  0:34   ` Bart Schaefer
2002-09-14  0:58   ` Philippe Troin
2002-09-14  4:56     ` Bart Schaefer
2002-09-16  4:58       ` Philippe Troin [this message]
2002-09-16  6:25         ` Bart Schaefer
2002-09-16 18:26           ` Philippe Troin
2002-09-16 20:46             ` Hans Dieter Pearcey
2002-09-17  0:08               ` Philippe Troin
2002-09-14 14:39   ` Peter Stephenson
2002-09-17 10:47     ` Peter Stephenson
2002-09-29 13:20     ` 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=87elbufs3q.fsf@ceramic.fifi.org \
    --to=phil@fifi.org \
    --cc=schaefer@brasslantern.com \
    --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).