From: Richard Jones <rich@annexia.org>
To: Christian Lindig <lindig@cs.uni-sb.de>
Cc: Caml List <caml-list@inria.fr>, caml-bugs@inria.fr
Subject: Re: [Caml-list] Bug? Random.int max_int on AMD64 fails
Date: Wed, 1 Jun 2005 09:58:14 +0100 [thread overview]
Message-ID: <20050601085814.GA17158@furbychan.cocan.org> (raw)
In-Reply-To: <c40bd2df651d41ea861d7e2d665a86cc@cs.uni-sb.de>
On Wed, Jun 01, 2005 at 10:14:01AM +0200, Christian Lindig wrote:
> ># Random.int max_int;;
> >Exception: Invalid_argument "Random.int".
> >#
The documentation states:
(** [Random.int bound] returns a random integer between 0 (inclusive)
and [bound] (exclusive). [bound] must be more than 0 and less
than 2{^30}. *)
On 64 bit machines, max_int is 2^62 or thereabouts.
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
next prev parent reply other threads:[~2005-06-01 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 8:14 Christian Lindig
2005-06-01 8:58 ` Richard Jones [this message]
2005-06-01 12:27 ` [Caml-list] " Jean-Christophe Filliatre
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=20050601085814.GA17158@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-bugs@inria.fr \
--cc=caml-list@inria.fr \
--cc=lindig@cs.uni-sb.de \
/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;
as well as URLs for NNTP newsgroup(s).