From: Stephane Chazelas <Stephane_Chazelas@yahoo.fr>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: arithmetic operator precedence
Date: Thu, 19 Jun 2008 17:27:18 +0100 [thread overview]
Message-ID: <20080619162718.GG5016@sc.homeunix.net> (raw)
In-Reply-To: <237967ef0806190910q70c0d0d7y2466938b547a8ee4@mail.gmail.com>
On Thu, Jun 19, 2008 at 06:10:56PM +0200, Mikael Magnusson wrote:
> 2008/6/19 Vincent Lefevre <vincent@vinc17.org>:
> > On 2008-06-19 14:29:03 +0200, Richard Hartmann wrote:
> >> On Thu, Jun 19, 2008 at 11:58, Peter Stephenson <pws@csr.com> wrote:
> >> > That seems a good idea in any case.
> >>
> >> Can you add that this is done to remain both backwards and shell-
> >> compatible and that this is not what a 'real' language/calculator
> >> will do?
> >
> > This isn't shell-compatible. AFAIK, only bash and ksh93 support **.
> >
> >> Perhaps even include a reference to the POSIX argument.
> >
> > There's no POSIX argument. ** is just an extension.
>
> I've followed this discussion, and I'm left wondering only one thing.
> If it's decided that $(( -1 ** 2 )) == 1, then what's the point? Why
> would anyone ever write that? Why require everyone to write -(1**2) when
> the expression makes no sense at all without the parentheses? Ie you would
> just write 1**2 without the - at all, nobody would ever write (-1)**2.
[...]
Think of:
double() {
REPLY=$(($1 * 2))
}
square() {
REPLY=$(($1 ** 2))
}
Where those functions are meant to be passed a number, positive
or negative, not any random arithmetic expression.
If you make ** have higher precedence than unary "-", then
square -1
returns -1
while double -1 returns -2 as expected.
--
Stéphane
next prev parent reply other threads:[~2008-06-19 16:27 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
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 [this message]
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=20080619162718.GG5016@sc.homeunix.net \
--to=stephane_chazelas@yahoo.fr \
--cc=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).