From: Clinton Bunch <cdb_zsh@zentaur.org>
To: zsh-workers@zsh.org
Subject: Re: further discussion of zsh/random (was [PATCH] zsh/random module [UPDATED])
Date: Mon, 28 Nov 2022 10:37:42 -0600 [thread overview]
Message-ID: <c81b8a26-d78f-89be-e06f-2fb3b8a541b2@zentaur.org> (raw)
In-Reply-To: <20221125094018.7ssecb3fppzusnmi@chazelas.org>
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
Having read all the criticism of the API, I still don't agree with the
minimalist view nor do I favor implementing a mathfunc to mirror a
semi-obscure API, and prefer to keep SRANDOM in a module that fails to
load if no kernel random source is available so I'm proposing a new API.
builtin:
zrandint -c /count/=*1 *-U /upper/=*MAX_UINT32 *-L /lower/=*0 *-s
/scalar /-a /array /-f raw|hex|*dec*
**default output is equivalent to _echo $SRANDOM_. I can special case
the nonsensical arguments like /count/=0 and /upper/=/lower /if that's
the wish of the group/. upper/ is inclusive
zrandbyte -c /count/=*8 *-s /scalar /-a /array /-f raw|hex|*hex:*|dec:
default output format will be a colon-separated string of bytes
encoded in hex, in an array hex and hex: are equivalent. I could,
instead, add another option to specify a separator and default to :.
Parameter:
SRANDOM
A random, uniformly-distributed, unsigned, 32-bit integer.
mathfunc:
zrandomf()
produces a random float-point number from 0 to 1 inclusive
zrandomi(/upper/=*MAX_UINT32*,/lower/=*0*,/inclusive/=*0*)
takes 0 to 3 arguments. exclusive by default to accommodate
${string[zrandomi($#string)+1]}
I'm not particularly tied to any of the names except SRANDOM
[-- Attachment #2: Type: text/html, Size: 2425 bytes --]
next prev parent reply other threads:[~2022-11-28 16:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 17:13 [PATCH] zsh/random module Clinton Bunch
2022-11-03 17:50 ` Bart Schaefer
2022-11-04 3:17 ` dana
2022-11-04 6:22 ` Clinton Bunch
2022-11-04 7:27 ` dana
2022-11-04 12:57 ` Clinton Bunch
2022-11-08 0:18 ` [PATCH] zsh/random module [UPDATED] Clinton Bunch
2022-11-18 14:30 ` Clinton Bunch
2022-11-19 6:42 ` Lawrence Velázquez
2022-11-18 16:23 ` Stephane Chazelas
2022-11-18 17:08 ` Clinton Bunch
2022-11-18 18:12 ` Stephane Chazelas
2022-11-18 18:38 ` Clinton Bunch
2022-11-23 19:52 ` Daniel Shahaf
2022-11-24 16:19 ` Stephane Chazelas
2022-11-24 16:30 ` Roman Perepelitsa
2022-11-24 22:39 ` Clinton Bunch
2022-11-25 8:53 ` Stephane Chazelas
2022-11-25 9:40 ` Stephane Chazelas
2022-11-28 16:37 ` Clinton Bunch [this message]
2022-11-21 1:07 ` Matthew Martin
2022-11-21 1:59 ` Clinton Bunch
2022-11-21 2:21 ` Matthew Martin
2022-11-21 2:57 ` Clinton Bunch
2022-11-21 3:14 ` Lawrence Velázquez
2022-11-21 4:17 ` Bart Schaefer
2022-11-21 5:05 ` Clinton Bunch
2022-11-22 13:42 ` dana
2022-11-23 19:49 ` Daniel Shahaf
2022-11-22 17:44 ` Oliver Kiddle
2022-11-22 19:48 ` Clinton Bunch
2022-11-23 1:23 ` Matthew Martin
2022-11-23 2:58 ` Clinton Bunch
2022-11-23 4:14 ` Matthew Martin
2022-11-23 13:41 ` Clinton Bunch
2022-11-23 20:33 ` Daniel Shahaf
2022-11-23 21:42 ` dana
2022-11-23 23:54 ` Daniel Shahaf
2022-11-24 0:17 ` Daniel Shahaf
2022-11-24 1:05 ` dana
2022-11-24 13:52 ` Clinton Bunch
2022-11-23 19:46 ` Daniel Shahaf
2022-11-24 2:58 ` Clinton Bunch
2022-11-24 10:07 ` nimaje+zml
2022-11-24 13:19 ` Clinton Bunch
2022-11-24 14:33 ` Clinton Bunch
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=c81b8a26-d78f-89be-e06f-2fb3b8a541b2@zentaur.org \
--to=cdb_zsh@zentaur.org \
--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).