From: "Mikael Magnusson" <mikachu@gmail.com>
To: "Zsh hackers list" <zsh-workers@sunsite.dk>
Subject: Re: arithmetic operator precedence
Date: Thu, 12 Jun 2008 15:12:34 +0200 [thread overview]
Message-ID: <237967ef0806120612k222d0ddel87058765bcf31e0c@mail.gmail.com> (raw)
In-Reply-To: <20080612095723.GF5113@sc.homeunix.net>
2008/6/12 Stephane Chazelas <Stephane_Chazelas@yahoo.fr>:
> $ zsh -c 'echo $(( 1 & 2 == 2 ))'
> 0
>
> "==" is meant to have precedence over &, so the above should
> give 1 as in C I think. All other shells do.
>From the manual:
An arithmetic expression uses nearly the same syntax,
precedence, and associativ-
ity of expressions in C. The following operators are
supported (listed in
decreasing order of precedence):
+ - ! ~ ++ --
unary plus/minus, logical NOT, complement,
{pre,post}{in,de}crement
<< >> bitwise shift left, right
& bitwise AND
^ bitwise XOR
| bitwise OR
** exponentiation
* / % multiplication, division, modulus (remainder)
+ - addition, subtraction
< > <= >=
comparison
== != equality and inequality
&& logical AND
|| ^^ logical OR, XOR
? : ternary operator
= += -= *= /= %= &= ^= |= <<= >>= &&= ||= ^^= **=
assignment
, comma operator
The operators `&&', `||', `&&=', and `||=' are
short-circuiting, and only one of
the latter two expressions in a ternary operator is evaluated.
Note the prece-
dence of the bitwise AND, OR, and XOR operators.
--
Mikael Magnusson
next prev parent reply other threads:[~2008-06-12 13:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 9:57 Stephane Chazelas
2008-06-12 13:12 ` Mikael Magnusson [this message]
2008-06-12 13:40 ` Peter Stephenson
2008-06-12 14:47 ` Bart Schaefer
2008-06-12 15:01 ` Stephane Chazelas
2008-06-16 8:17 ` Vincent Lefevre
2008-06-16 8:07 ` Vincent Lefevre
2008-06-16 13:42 ` Peter Stephenson
2008-06-16 13:59 ` Stephane Chazelas
2008-06-16 14:33 ` Vincent Lefevre
2008-06-17 9:19 ` Richard Hartmann
2008-06-17 9:45 ` Stephane Chazelas
2008-06-17 10:24 ` Richard Hartmann
2008-06-17 10:24 ` Richard Hartmann
2008-06-17 10:38 ` Stephane Chazelas
2008-06-17 10:43 ` Peter Stephenson
2008-06-17 11:28 ` Vincent Lefevre
2008-06-17 11:46 ` Peter Stephenson
2008-06-17 12:05 ` Vincent Lefevre
2008-06-19 9:37 ` Jun T.
2008-06-19 9:54 ` Stephane Chazelas
2008-06-19 16:00 ` Vincent Lefevre
2008-06-19 16:20 ` Stephane Chazelas
2008-06-19 17:14 ` Vincent Lefevre
2008-06-19 9:58 ` Peter Stephenson
2008-06-19 12:29 ` Richard Hartmann
2008-06-19 16:04 ` Vincent Lefevre
2008-06-19 16:10 ` Mikael Magnusson
2008-06-19 16:27 ` Stephane Chazelas
2008-06-19 17:25 ` Vincent Lefevre
2008-06-19 17:20 ` Vincent Lefevre
2008-06-17 10:45 ` Richard Hartmann
2008-06-17 11:38 ` Vincent Lefevre
2008-06-17 11:19 ` Vincent Lefevre
2008-06-17 11:57 ` Stephane Chazelas
2008-06-17 12:35 ` Vincent Lefevre
2008-06-17 12:46 ` Stephane Chazelas
2008-06-17 13:02 ` Vincent Lefevre
2008-06-17 13:20 ` Stephane Chazelas
2008-06-17 14:33 ` Vincent Lefevre
2008-06-17 14:53 ` Stephane Chazelas
2008-06-17 15:49 ` Vincent Lefevre
2008-06-17 14:35 ` Stephane Chazelas
2008-06-17 15:05 ` Vincent Lefevre
2008-06-17 10:54 ` Vincent Lefevre
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=237967ef0806120612k222d0ddel87058765bcf31e0c@mail.gmail.com \
--to=mikachu@gmail.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).