From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: use of rand() in zsh
Date: Tue, 11 Oct 2022 14:18:56 +0100 (BST) [thread overview]
Message-ID: <1046616417.2639901.1665494336416@mail.virginmedia.com> (raw)
In-Reply-To: <8918db54-3687-b26e-4a04-1a8814b11f86@zentaur.org>
> On 11/10/2022 13:35 Clinton Bunch <cdb_zsh@zentaur.org> wrote:
> On 10/10/2022 8:14 PM, Bart Schaefer wrote:
> > On Mon, Oct 10, 2022 at 4:38 PM Clinton Bunch <cdb_zsh@zentaur.org> wrote:
> >> Is there a reason that zsh goes out of the way (srand_deterministic) to
> >> use the least random "random" function on modern Unix?
> >
> > This is e.g. so you aren't surprised by referencing $RANDOM inside
> > $(...) and getting a different result.
> >
> Doesn't zsleep_random's use of rand() break this predictability, or have
> I just not studied the use of zsleep_random enough?
Yes, looks like any locking of history files will disturb the sequence.
That could be fairly easily fixed on a modern system by using rand_r here
--- history locking doesn't need high quality randomness, just
some sort of variation, so probably isn't worth reimplementing fully.
pws
prev parent reply other threads:[~2022-10-11 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 23:32 Clinton Bunch
2022-10-11 1:14 ` Bart Schaefer
2022-10-11 1:27 ` Clinton Bunch
2022-10-11 1:32 ` Clinton Bunch
2022-10-11 3:34 ` Bart Schaefer
2022-10-11 3:44 ` Clinton Bunch
2022-10-11 6:31 ` Roman Perepelitsa
2022-10-11 12:51 ` Clinton Bunch
2022-10-11 13:23 ` Peter Stephenson
2022-10-11 14:15 ` Clinton Bunch
2022-10-11 14:48 ` Peter Stephenson
2022-10-11 12:35 ` Clinton Bunch
2022-10-11 13:18 ` Peter Stephenson [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=1046616417.2639901.1665494336416@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).