From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: &&||
Date: Tue, 20 Feb 2018 11:24:41 -0800 [thread overview]
Message-ID: <dd60f68c-dddd-1ea3-bc4a-ebcb83173cdf@eastlink.ca> (raw)
In-Reply-To: <20180220170734.7f428bd6@pwslap01u.europe.root.pri>
On 20/02/18 09:07 AM, Peter Stephenson wrote:
> You've now extended your demand so that it works with an else clause as
Not 'extended' that is the entire point of my question. I'm expecting
the '||' to be identical to a logical 'else', there is no other issue.
Demand? I seek clarification, mind, if it were agreed that my sense of
the logic were correct I'd be happy to see it change, but issues of
logic and code flow are rigorous and not subject to opinion.
> You could do this, I suppose.
>
> first-statement && {
> any-old-stuff
> true << right, I see how that protects.
> } || {something-else-entirely}
Ok, I'm at least on guard for that sort of thing from now on. I've more and more been using &&|| constructions in place of if/else simply because the former is more compact, but I'll be more vigilant from now on. Braces are ignored as far as truth tests on the left of any && or ||. I can't say I like it tho, not that that matters, a thing like this is entirely at your discretion.
next prev parent reply other threads:[~2018-02-20 19:54 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 [this message]
2018-02-20 20:28 ` &&|| Bart Schaefer
2018-02-20 21:45 ` &&|| Ray Andrews
-- 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=dd60f68c-dddd-1ea3-bc4a-ebcb83173cdf@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).