From owner-cvs-all  Sun Feb 25 12:16:16 2001
Delivered-To: cvs-all@freebsd.org
Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65])
	by hub.freebsd.org (Postfix) with ESMTP
	id AD84E37B503; Sun, 25 Feb 2001 12:16:04 -0800 (PST)
	(envelope-from mark@grondar.za)
Received: from grondar.za (root@gratis.grondar.za [196.7.18.133])
	by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f1PKFvR02915;
	Sun, 25 Feb 2001 22:16:00 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <200102252016.f1PKFvR02915@gratis.grondar.za>
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: rand.c patch for review (was: Re: cvs commit: ports/astro/xglobe/files patch-random) 
References: <20010225125901.A47165@hamlet.nectar.com> 
In-Reply-To: <20010225125901.A47165@hamlet.nectar.com> ; from "Jacques A. Vidrine" <n@nectar.com>  "Sun, 25 Feb 2001 12:59:01 CST."
Date: Sun, 25 Feb 2001 22:16:42 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > 1) Seed & State. Even if srand() is backed by srandom(), if called
> > independently, they overwrite each other seeding
> > state. initstate() etc. adds more here.
> 
> Emphasis:  Standard C says that rand/srand must behave as if
> no other library functions ever call them.  i.e. the state must
> not change except when the application calls rand/srand.

OK - good answers. Whatever rand() we choose needs decent theory behind
it.

Andrey - you had something - what was its origin?

M
-- 
Mark Murray
Warning: this .sig is umop ap!sdn

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message