From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: unintuitive bracketing with return value
Date: Tue, 18 Oct 2022 10:57:49 -0700 [thread overview]
Message-ID: <22aaa8cc-48e9-90fc-f006-e8534858816d@eastlink.ca> (raw)
In-Reply-To: <0ea47ef0-f039-41db-4514-b5b70045a9ef@gmx.com>
On 2022-10-18 07:57, Eric Cook wrote:
>
> https://mywiki.wooledge.org/BashPitfalls#pf22
>
Very well written! What breaks my intuition tho is the brackets.
Otherwise I quite understand that the last exit value is the active
one. I'm expecting the brackets to 'contain' the rv of any commands
within the brackets. But no, the left > right rule applies and the
brackets don't make any difference.
Roman:
1. Is the result coerced to bool (0 or 1)? Yes in C (and other
statically-typed languages), no in Zsh (and other dynamically-typed
languages).
2. Does && have higher precedence than ||? Yes in C (and most
languages), no in Zsh (and all shells).
... Even after all these years I still think in C. And, as Peter
explains, the braces don't really change anything at all, the last rv is
still the last rv. Indeed, it's best to stick with if/else and avoid
these little things. I really shouldn't have to have these basics
explained over and over :(
next prev parent reply other threads:[~2022-10-18 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 14:47 Ray Andrews
2022-10-18 14:57 ` Eric Cook
2022-10-18 17:57 ` Ray Andrews [this message]
2022-10-18 19:32 ` Lawrence Velázquez
2022-10-18 20:12 ` Bart Schaefer
2022-10-18 20:14 ` Bart Schaefer
2022-10-18 20:22 ` Ray Andrews
2022-10-18 20:31 ` Clinton Bunch
2022-10-18 16:07 ` Roman Perepelitsa
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=22aaa8cc-48e9-90fc-f006-e8534858816d@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).