From: Stephen Dolan <stephen.dolan@cl.cam.ac.uk>
To: Hannes Mehnert <hannes@mehnert.org>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] behaviour of mod
Date: Mon, 19 Jan 2015 10:59:43 +0000 [thread overview]
Message-ID: <CA+mHimPfz8R6gKeGBzLP2RATEFLv8jOj-Bdd0Cvrfo08YgS2Zw@mail.gmail.com> (raw)
In-Reply-To: <54BBFFF7.6030106@mehnert.org>
On Sun, Jan 18, 2015 at 6:48 PM, Hannes Mehnert <hannes@mehnert.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA384
>
> Hi,
>
> is the behaviour of modulo arithmetics intentional:
> -5 mod 4 = -1 ?
>
> While this reflects the C behaviour, my expectation was to always have
> a positive result:
> -5 mod 4 = 3
>
> Any hints?
Given OCaml's integer division operator, this is the correct "mod".
The important property is:
(x / y) * y + (x mod y) = x
In other words, (x mod y) gives the error by which (x / y) * y fails to equal x.
There are two reasonable (/, mod) pairs which have this behaviour. The
first, which C and OCaml use, is where (x / y) rounds towards zero and
(x mod y) has the same sign as x, so -5 / 4 = -1 and -5 mod 4 = -1.
The second is where (x / y) rounds down and (x mod y) has the same
sign as y, so -5 / 4 = -2 and -5 mod 4 = 3.
Subjectively, I think the first division operator (round-toward-zero,
aka truncate) and the second modulo operator are the more natural. The
second modulo operator actually implements modular arithmetic, since
with it x mod n buckets the integers x into n equivalence classes
differing by multiples of n. But using the first (/) and the second
mod breaks the remainder property above.
Incidentally, Haskell provides both: the first is called (quot, rem)
while the second is (div, mod).
Stephen
next prev parent reply other threads:[~2015-01-19 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 18:48 Hannes Mehnert
2015-01-18 19:28 ` Gabriel Scherer
2015-01-18 21:06 ` Mr. Herr
2015-01-19 10:59 ` Stephen Dolan [this message]
2015-01-20 21:57 ` Yaron Minsky
2015-01-20 21:57 ` Yaron Minsky
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=CA+mHimPfz8R6gKeGBzLP2RATEFLv8jOj-Bdd0Cvrfo08YgS2Zw@mail.gmail.com \
--to=stephen.dolan@cl.cam.ac.uk \
--cc=caml-list@inria.fr \
--cc=hannes@mehnert.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox