manual page first distributed with 4.2BSD
[unix-history] / usr / src / lib / libc / stdlib / random.3
CommitLineData
7db0d200
KM
1.\" Copyright (c) 1983 Regents of the University of California.
2.\" All rights reserved. The Berkeley software License Agreement
3.\" specifies the terms and conditions for redistribution.
4.\"
5.\" @(#)random.3 5.1 (Berkeley) %G%
6.\"
7.TH RANDOM 3 "19 January 1983"
8.UC 5
9.SH NAME
10random, srandom, initstate, setstate \- better random number generator; routines for changing generators
11.SH SYNOPSIS
12.nf
13.B long random()
14.PP
15.B srandom(seed)
16.B int seed;
17.PP
18.B char *initstate(seed, state, n)
19.B unsigned seed;
20.B char *state;
21.B int n;
22.PP
23.B char *setstate(state)
24.B char *state;
25.fi
26.SH DESCRIPTION
27.PP
28.I Random
29uses a non-linear additive feedback random number generator employing a
30default table of size 31 long integers to return successive pseudo-random
31numbers in the range from 0 to 2\u\s731\s10\d\-1. The period of this
32random number generator is very large, approximately 16*(2\u\s731\s10\d\-1).
33.PP
34.I Random/srandom
35have (almost) the same calling sequence and initialization properties as
36.I rand/srand.
37The difference is that
38.IR rand (3)
39produces a much less random sequence -- in fact, the low dozen bits
40generated by rand go through a cyclic pattern. All the bits generated by
41.I random
42are usable. For example, \*(lqrandom()&01\*(rq will produce a random binary
43value.
44.PP
45Unlike
46.IR srand ,
47.I srandom
48does not return the old seed; the reason for this is that the amount of
49state information used is much more than a single word. (Two other
50routines are provided to deal with restarting/changing random
51number generators). Like
52.IR rand (3),
53however,
54.I random
55will by default produce a sequence of numbers that can be duplicated
56by calling
57.I srandom
58with
59.I 1
60as the seed.
61.PP
62The
63.I initstate
64routine allows a state array, passed in as an argument, to be initialized
65for future use. The size of the state array (in bytes) is used by
66.I initstate
67to decide how sophisticated a random number generator it should use -- the
68more state, the better the random numbers will be.
69(Current "optimal" values for the amount of state information are
708, 32, 64, 128, and 256 bytes; other amounts will be rounded down to
71the nearest known amount. Using less than 8 bytes will cause an error).
72The seed for the initialization (which specifies a starting point for
73the random number sequence, and provides for restarting at the same
74point) is also an argument.
75.I Initstate
76returns a pointer to the previous state information array.
77.PP
78Once a state has been initialized, the
79.I setstate
80routine provides for rapid switching between states.
81.I Setstate returns a pointer to the previous state array; its
82argument state array is used for further random number generation
83until the next call to
84.I initstate
85or
86.I setstate.
87.PP
88Once a state array has been initialized, it may be restarted at a
89different point either by calling
90.I initstate
91(with the desired seed, the state array, and its size) or by calling
92both
93.I setstate
94(with the state array) and
95.I srandom
96(with the desired seed).
97The advantage of calling both
98.I setstate
99and
100.I srandom
101is that the size of the state array does not have to be remembered after
102it is initialized.
103.PP
104With 256 bytes of state information, the period of the random number
105generator is greater than 2\u\s769\s10\d, which should be sufficient for
106most purposes.
107.SH AUTHOR
108Earl T. Cohen
109.SH DIAGNOSTICS
110.PP
111If
112.I initstate
113is called with less than 8 bytes of state information, or if
114.I setstate
115detects that the state information has been garbled, error
116messages are printed on the standard error output.
117.SH "SEE ALSO"
118rand(3)
119.SH BUGS
120About 2/3 the speed of
121.IR rand (3C).