* rand.c (rand32): Bugfix: if the seed object is a random

state, we do not want to make the 8 calls to rand32 to
mix up the state; we need are making a straight copy.

* txr.1: Document the possibility that the seed object
is a random state. Document the platform-independence of the
integer seed.

1 files changed, 10 insertions, 1 deletions

diff --git a/txr.1 b/txr.1
index 0c3ab384..33cfdfee 100644
--- a/txr.1
+++ b/txr.1
@@ -22992,7 +22992,8 @@ an object of the same kind as what is stored in the
 .code *random-state*
 variable.
 
-The seed, if specified, must be an integer value.
+The seed, if specified, must be either an integer value, or an
+existing random state object.
 
 Note that the sign of the seed is ignored, so that negative seed
 values are equivalent to their additive inverses.
@@ -23010,6 +23011,14 @@ On a platform with a millisecond-resolution real-time clock, the minimum
 time increment is a millisecond. Calls to make-random-state less than
 a millisecond apart may predictably produce the same seed.
 
+If an integer seed is specified, then the integer value is mapped to a
+pseudo-random sequence, in a platform-independent way.
+
+If a random state is specified as a seed, then it is duplicated. The
+returned random state object is a distinct object which is in the same
+state as the input object. It will produce the same remaining pseudo-random
+number sequence, as will the input object.
+
 .coNP Function @ random-state-p
 .synb
 .mets (random-state-p << obj )