From owner-freebsd-current Mon Oct 7 11:36:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16734 for current-outgoing; Mon, 7 Oct 1996 11:36:34 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA16728; Mon, 7 Oct 1996 11:36:32 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA17544; Mon, 7 Oct 1996 11:23:20 -0700 Date: Mon, 7 Oct 1996 11:23:20 -0700 (PDT) From: "Brian N. Handy" To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= Cc: Terry Lambert , joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, Bruce Evans Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610071720.VAA01227@nagual.ru> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hey all, I'm trying to stay on top of this thread and follow all the theories, and I'll throw in my two cents -- It's important to recall Andrey wanted to change random() originally in part because the Gimp folks (and probably others) complain that our random() is really too non-random(). I've done a fair amount of fiddling with random number generators in my time, and I think it's safe to say there's no way it's going to get improved to the point where the numerical folks are happy. Jordan hit this one squarely on the head. Hence most of them use their own random number generator. I don't know anyone that depends on the routine that comes with the system. That's almost scary. There's been one suggestion to write another random number generator and not changing the old one. I don't think that's going to fix anything, since in general the software driving this change (GIMP et al) is all going to have to have small ugly hacks in them to support it. It would be nicer if our random() just worked. So, following in this line of reasoning, I support fixing random(). Regards, Brian