zsh-workers
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.org>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Cc: Richard Hartmann <richih.mailinglist@gmail.com>,
	Peter Stephenson <p.w.stephenson@ntlworld.com>
Subject: Re: arithmetic operator precedence
Date: Tue, 17 Jun 2008 13:38:32 +0200	[thread overview]
Message-ID: <20080617113832.GG10734@prunille.vinc17.org> (raw)
In-Reply-To: <20080617103829.GD5016@sc.homeunix.net>

On 2008-06-17 11:38:29 +0100, Stephane Chazelas wrote:
> What I meant is that ^ reminds of the /human/ (as opposed to
> /computer/) representation as it indicates that follows must be
> raised up as in 3². So, one can understand that it should follow
> the same rules (that is -3^2 should be the same as -3², even
> though that's not what POSIX decided for bc). But given that **
> has more the shape of the * operator, I'm not sure we can tell
> the same thing.

Note that in math, -(a * b) and (-a) * b are equivalent (even in
the general case of a ring), and I'd say that most people regard
- a * b more like -(a * b) than (-a) * b. So, you can't really
compare to * without confusion.

Also ** is merely a replacement for the more conventional (and
shorter) ^ when ^ can't be used (e.g. because it already has
another meaning).

Math writing asside, the fact that -3**2 and 0-3**2 return different
results is quite confusing too.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)


  parent reply	other threads:[~2008-06-17 11:38 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
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 [this message]
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=20080617113832.GG10734@prunille.vinc17.org \
    --to=vincent@vinc17.org \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=richih.mailinglist@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).