From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: problems with RANDOM in subshells
Date: Thu, 31 Jan 2002 11:07:13 +0000 [thread overview]
Message-ID: <14374.1012475233@csr.com> (raw)
In-Reply-To: "Zefram"'s message of "Thu, 31 Jan 2002 03:46:51 GMT." <20020131034651.GB7382@fysh.org>
Zefram wrote:
> Clint Adams wrote:
> >Should the random-seeding behavior be changed for subshells?
>
> No. We define $RANDOM to be a PRNG; zshparam(1) speaks of seeding it
> (by writing to $RANDOM). Opening a subshell should not interfere with
> the PRNG sequence, which one might be relying on to be reproducible.
bash has the zsh behaviour, but ksh 88 handles subshells specially.
POSIX/SUS doesn't defined RANDOM, but we probably ought to get this
specified for David Korn's enhanced shell proposal, given that all three
shells under discussion already have RANDOM.
It does seem to me that it's unnecessarily hard for a user to take avoiding
action in a subshell. At least providing the PID of the subshell process
as separate parameter might give them the start, e.g. make $ZSH_REALPID map
directly to getpid() --- obviously not with a very high degree of
randomness, but I don't think that was a problem in this case. (The
advantage over providing a real `random' number is that it takes a minute
to write instead of a day.)
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 392070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
prev parent reply other threads:[~2002-01-31 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 3:20 Clint Adams
2002-01-31 3:46 ` Zefram
2002-01-31 4:03 ` Bart Schaefer
2002-01-31 4:06 ` Bart Schaefer
2002-01-31 11:34 ` Peter Stephenson
2002-01-31 11:07 ` 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=14374.1012475233@csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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).