From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: &&||
Date: Tue, 20 Feb 2018 13:45:24 -0800 [thread overview]
Message-ID: <e202c5d8-6c84-9994-b71d-8167a88dfea8@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7ar21AnR89XtbtaTQtqZYJUvGsQzxcfkDvd2UqJ70=xMw@mail.gmail.com>
On 20/02/18 12:28 PM, Bart Schaefer wrote:
That was a master class in logic. Thank you Sensei.
>> ignored as far as truth tests on the left of any && or ||.
> No, that's entirely wrong. Braces always return the final status of
> the enclosed list of statements. && and || always use the final
> status of the entire chain of any && or || to their left. The two are
> related only when the braces surround another chain of && or || but
> only in so far as that affects the final status of the braces.
Yes, I get it. I was asking/expecting the braces to throw decision
leftward to the preceding '&&' whereas they properly create a { combined
truth test } to be thrown rightward to the following '||' exactly as
they should!
So the fact that one can often set up an &&/|| structure that looks very
much like an if/else structure, and the fact that they will very often
behave the same way, does not make them logically identical!! I feel
purified of a sin ;-)
Thanks Peter too, I know I flog these things to death.
>
next prev parent reply other threads:[~2018-02-20 21:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 21:12 &&|| Ray Andrews
2018-02-19 21:57 ` &&|| Peter Stephenson
2018-02-19 22:47 ` &&|| Ray Andrews
2018-02-20 9:26 ` &&|| Peter Stephenson
2018-02-20 7:54 ` &&|| Ray Andrews
2018-02-20 17:07 ` &&|| Peter Stephenson
2018-02-20 19:24 ` &&|| Ray Andrews
2018-02-20 20:28 ` &&|| Bart Schaefer
2018-02-20 21:45 ` Ray Andrews [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 13:45 !!:$ keef
2004-11-16 14:22 ` !!:$ Peter Stephenson
2004-11-16 14:31 ` !!:$ Stephane Chazelas
2004-11-16 15:37 ` !!:$ Bart Schaefer
2004-11-16 16:08 ` !!:$ Peter Stephenson
2004-11-17 0:03 ` !!:$ Bart Schaefer
2004-11-17 19:25 ` !!:$ Danek Duvall
2004-11-18 1:10 ` !!:$ Bart Schaefer
2003-07-02 15:06 ?????? JEFF BICKLEY
2003-07-02 19:56 ` ?????? Thorsten Haude
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=e202c5d8-6c84-9994-b71d-8167a88dfea8@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).