From: Andrew <newsgroups.fr@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] portablility of random.mli in the stdlib
Date: Sat, 30 Apr 2011 15:33:35 +0200 [thread overview]
Message-ID: <4DBC0FAF.8030200@gmail.com> (raw)
In-Reply-To: <4DBBF1D8.6020105@gmail.com>
> Why should a random generator give the same results over multiple
> versions and architectures?
> Starting from same seed is useful only for debugging.
>
In designing a game, you might find it convenient to use a given seed to encode a sequence of numbers (eg. level one is
random seed 1524).
Another field where that could be useful is statistics; being able to reproduce your results is absolutely crucial.
Taking random values is fine, but you can' just say you obtained a result without telling others how to reproduce it.
Andrew.
prev parent reply other threads:[~2011-04-30 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 10:37 Christophe Raffalli
2011-04-30 11:14 ` Christophe Raffalli
2011-04-30 11:26 ` Török Edwin
2011-04-30 11:42 ` Christophe Raffalli
2011-04-30 15:38 ` Andrei Formiga
2011-04-30 12:06 ` Alexandre Pilkiewicz
2011-04-30 13:33 ` Andrew [this message]
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=4DBC0FAF.8030200@gmail.com \
--to=newsgroups.fr@gmail.com \
--cc=caml-list@inria.fr \
/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