From: Stephane Chazelas <Stephane_Chazelas@yahoo.fr>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: arithmetic operator precedence
Date: Thu, 12 Jun 2008 16:01:26 +0100 [thread overview]
Message-ID: <20080612150126.GH5113@sc.homeunix.net> (raw)
In-Reply-To: <080612074751.ZM8185@torch.brasslantern.com>
On Thu, Jun 12, 2008 at 07:47:51AM -0700, Bart Schaefer wrote:
> On Jun 12, 2:40pm, Peter Stephenson wrote:
> } Subject: Re: arithmetic operator precedence
> }
> } On Thu, 12 Jun 2008 10:57:23 +0100
> } Stephane Chazelas <Stephane_Chazelas@yahoo.fr> wrote:
> } > "==" is meant to have precedence over &, so the above should
> } > give 1 as in C I think. All other shells do.
> }
> } This is a fairly icky incompatibility
>
> What I'm struggling (although not very hard) to remember is why Paul
> would have chosen a non-standard precedence in the first place.
I find the zsh precedence more intuitive but that's not of much
help given that I get to use those binary operators mostly only
in C/perl, so I have to know the C precedence anyway.
And having zsh behaving differently doesn't help at all.
Actually, I reported that bug because I wanted to double check
what the C precedence was for & vs ==. I thought that was one of
those unintuitive cases where "==" had precedence, but in doubt,
I checked with zsh's $((...)) that told me I was wrong.
Fortunately, I did reread the C precedence chart and tried with
another shell, otherwise I'd have been fooled by zsh...
But I now know that zsh's precedence is not the same as
elsewhere so I hopefully won't be fooled again.
--
Stéphane
next prev parent reply other threads:[~2008-06-12 15:01 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
2008-06-12 13:40 ` Peter Stephenson
2008-06-12 14:47 ` Bart Schaefer
2008-06-12 15:01 ` Stephane Chazelas [this message]
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=20080612150126.GH5113@sc.homeunix.net \
--to=stephane_chazelas@yahoo.fr \
--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).