From: David Kastrup <dak@gnu.org>
To: guile-devel@gnu.org
Subject: Re: Improve `seed->random-state' in stable-2.0?
Date: Sat, 21 Jan 2012 08:38:42 +0100 [thread overview]
Message-ID: <87d3adld31.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87ehuuuh6x.fsf@netris.org
Mark H Weaver <mhw@netris.org> writes:
> Can't we just make a clean break now? 2.0 is still not widely
> deployed, so now is a great time to assert our right to change the
> PRNG at will. As you say, it's unlikely that anyone is relying on
> this anyway. If anyone is, wouldn't it be better to deal with that
> now?
For unique identifier generation, you want a PRNG that has a period
equal to the size of the generated identifier set and generates the same
next value given the current value in order to avoid the birthday
paradoxon. That is actually different from what one considers a "good
PRNG", so it might make sense to have a home-brewn "bad PRNG" for this
purpose.
Actually, you don't need a PRNG at all. Generate a _good_ random
starting value, and count sequentially from there. The probability of
collision is the same as with a pseudo-random sequence, but if there
happens to be a problem at any time, it becomes much easier to diagnose.
--
David Kastrup
next prev parent reply other threads:[~2012-01-21 7:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 3:28 Improve `seed->random-state' in stable-2.0? Mark H Weaver
2012-01-20 8:37 ` David Kastrup
2012-01-20 14:54 ` Andy Wingo
2012-01-20 18:52 ` Mark H Weaver
2012-01-20 20:35 ` Andy Wingo
2012-01-20 22:45 ` Mark H Weaver
2012-01-21 7:38 ` David Kastrup [this message]
2012-01-21 8:20 ` Mark H Weaver
2012-01-23 9:52 ` Andy Wingo
2012-01-20 23:46 ` Mike Gran
2012-01-23 9:55 ` Andy Wingo
2012-01-23 13:06 ` Mike Gran
2012-01-23 14:06 ` Andy Wingo
2012-01-24 6:08 ` Mike Gran
2012-01-24 9:56 ` Andy Wingo
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3adld31.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).