From: Jay Belanger <jay.p.belanger@gmail.com>
To: Francis Litterio <flitterio@gmail.com>
Cc: jay.p.belanger@gmail.com, bug-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Re: In CVS Emacs, calc-eval gives multiplication higher precidence than division
Date: Sun, 07 Sep 2008 11:37:01 -0500 [thread overview]
Message-ID: <878wu3j4k2.fsf@gmail.com> (raw)
In-Reply-To: <i5i6ej3wue71.fsf@gmail.com> (Francis Litterio's message of "Sun, 07 Sep 2008 12:06:38 -0400")
Francis Litterio <flitterio@gmail.com> writes:
...
> In CVS Emacs, function calc-eval (in lisp/calc/calc.el) gives
> multiplication higher precidence than division.
That's not a bug. While many systems give division a higher precendence
than multiplication, that isn't a universal rule. Calc has always given
multiplication a higher precendence, and something like
1 / 2 * 1000
can be viewed as shorthand for
1
--------
2 * 1000
Some people don't like this, some people do, but this choice is
established Calc behavior and is highlighted in the manual. To divide
first, it's probably better style regardless to put in the parentheses:
(1 / 2) * 1000
Jay
next prev parent reply other threads:[~2008-09-07 16:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 16:06 In CVS Emacs, calc-eval gives multiplication higher precidence than division Francis Litterio
2008-09-07 16:37 ` Jay Belanger [this message]
2008-09-07 18:15 ` Francis Litterio
2008-09-07 19:46 ` Stefan Monnier
2008-09-07 20:19 ` bug#920: " Lennart Borgman (gmail)
2008-09-07 20:32 ` Randal L. Schwartz
2008-09-07 20:34 ` Lennart Borgman (gmail)
2008-09-07 20:38 ` Randal L. Schwartz
2008-09-07 20:42 ` Lennart Borgman (gmail)
2008-09-07 20:50 ` Randal L. Schwartz
2008-09-07 21:07 ` Lennart Borgman (gmail)
2008-09-08 6:39 ` Ulrich Mueller
2008-09-08 7:07 ` Lennart Borgman (gmail)
2008-09-07 21:10 ` Stefan Monnier
2008-09-07 23:30 ` Jay Belanger
2008-09-08 0:50 ` Jason Rumney
2008-09-08 1:13 ` Randal L. Schwartz
2008-09-08 3:47 ` Stefan Monnier
2008-09-08 8:48 ` Miles Bader
2008-09-08 12:59 ` Stefan Monnier
2008-09-08 13:29 ` martin rudalics
2008-09-08 7:26 ` Lennart Borgman (gmail)
2008-09-07 21:10 ` Stefan Monnier
2008-09-08 10:30 ` Carsten Dominik
2008-09-08 11:01 ` Lennart Borgman
2008-09-08 20:33 ` Carsten Dominik
2008-09-08 20:39 ` Lennart Borgman (gmail)
2008-09-08 20:43 ` Randal L. Schwartz
2008-09-08 20:53 ` Lennart Borgman (gmail)
2008-09-08 22:59 ` bug#914: " Jay Belanger
2008-09-08 23:44 ` Lennart Borgman (gmail)
2008-09-09 13:28 ` Stefan Monnier
2008-09-09 14:36 ` Francis Litterio
2008-09-09 16:26 ` Ulrich Mueller
2008-09-09 16:41 ` Lennart Borgman (gmail)
2008-09-30 4:10 ` Leo
2008-09-08 21:42 ` Stefan Monnier
2008-09-09 8:11 ` Richard M. Stallman
2008-09-09 13:26 ` Stefan Monnier
2008-09-09 17:03 ` Lennart Borgman (gmail)
2008-09-09 17:19 ` Stefan Monnier
2008-09-08 13:01 ` Stefan Monnier
2008-09-07 20:35 ` Jay Belanger
2008-09-07 21:15 ` Stefan Monnier
2008-09-07 21:19 ` Lennart Borgman (gmail)
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878wu3j4k2.fsf@gmail.com \
--to=jay.p.belanger@gmail.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=flitterio@gmail.com \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).