Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 70430 invoked by uid 500); 16 May 2003 13:56:52 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 70370 invoked from network); 16 May 2003 13:56:51 -0000 Message-ID: <3EC4EE23.6050409@algroup.co.uk> Date: Fri, 16 May 2003 14:56:51 +0100 From: Ben Laurie User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: APR Dev List Subject: PRNG X-Enigmail-Version: 0.74.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N It has been suggested that I should make my new PRNG (as yet unwritten) a part of APR, since the original motivation was to fix the UUID problems in APR. I'm more than happy to do that, it seems like the best way to get the cross-platform support it needs, and it does mean there's one less dependency for APR. So, what do others think about this? Cheers, Ben. -- http://www.apache-ssl.org/ben.html http://www.thebunker.net/ "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff