unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Leo <sdl.web@gmail.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 9118@debbugs.gnu.org
Subject: bug#9118: 23.3.50; Don't seed the RNG in message-unique-id
Date: Thu, 21 Jul 2011 13:57:51 +0200	[thread overview]
Message-ID: <CAAeL0ST2yo83x0F0kH3zQP_7WMkjD1R8Gak=fe7Lvxo_CWG9mQ@mail.gmail.com> (raw)
In-Reply-To: <m1hb6g2qdw.fsf@gmail.com>

On Thu, Jul 21, 2011 at 06:45, Leo <sdl.web@gmail.com> wrote:

> Indeed, some do some don't. I wonder if Emacs should?

Many systems (languages, etc.) have a facility to seed the RNG with a
specific seed (saved from a previous run, for example), so you can
have repeated runs with the exact same sequence of random numbers, if
needed. That can be useful for simulation, testing, etc.

AFAIK, the Emacs RNG does not allow that at the lisp level, so it
would be better to automatically seed it and remove the many (random
t) calls, which, as has been pointed out, can in fact be harmful for
the quality of the generated random number series, if called
repeatedly.

    Juanma





  reply	other threads:[~2011-07-21 11:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 16:42 bug#9118: 23.3.50; Don't seed the RNG in message-unique-id Leo
2011-07-19 14:57 ` Lars Magne Ingebrigtsen
2011-07-19 15:14   ` Leo
2011-07-19 15:24     ` Lars Magne Ingebrigtsen
2011-07-19 15:44       ` Leo
2011-07-19 15:49         ` Lars Magne Ingebrigtsen
2011-07-20  2:12           ` Leo
2011-07-20 20:28             ` Lars Magne Ingebrigtsen
2011-07-21  4:45               ` Leo
2011-07-21 11:57                 ` Juanma Barranquero [this message]
2011-07-21 15:58                   ` Leo
2011-07-31 15:39                     ` Lars Magne Ingebrigtsen
2011-07-31 16:02                       ` Leo

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='CAAeL0ST2yo83x0F0kH3zQP_7WMkjD1R8Gak=fe7Lvxo_CWG9mQ@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=9118@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=sdl.web@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).