Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117097 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 94108 invoked from network); 21 Feb 2022 11:24:51 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 21 Feb 2022 11:24:51 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 09E4B180539 for ; Mon, 21 Feb 2022 04:44:05 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS24940 176.9.0.0/16 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 21 Feb 2022 04:44:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1645447443; bh=bWEupbnvlJFruFy8dfy+jQCepYhFoFcOLQ7PRG4c0Bw=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=cU5yi5f++qvBDwi7EO07S+c+FPi+kmt6MG4f3xGVAe6WmcxgsX2FyD17iBnjUltf+ R4i0/i9r00nzeVnq865pPHAN29+yek0MjXh0mwUsLmzCclE8z+q1QXDBi+Uei1RcF6 51CNBxnI5U9tK6vnHll5GLHYSQXH+NCI8g+MEigFvy8vfgjvQ2r6O1FBpElWWRnCEE d5pLQoityD9ESj+52ATXeZlfxlGWwDvnU2sLYSu1bq5FquYLzpUs0leh1jOyteYSjJ 6PtBrhqEMByuXxaEjaaYk+c2pxOu0KsHHcX4MiZBXoMkCc/zLoLTDBvjcuaR14v7oO HS+TfxERf9uPQ== Message-ID: <47cb96f5-4450-0377-dc95-67faac3fef33@bastelstu.be> Date: Mon, 21 Feb 2022 13:44:02 +0100 MIME-Version: 1.0 Content-Language: en-US To: Go Kudo Cc: internals@lists.php.net References: <553ba7ca-3821-c2d9-f88f-b216013a887b@bastelstu.be> <2c667812-88c8-0b7b-3558-561a1348d0b2@bastelstu.be> <5f496cf9-8754-b009-9cb5-b978222b2249@bastelstu.be> <26a8c3ee-9f0a-793c-10c0-7e642eedf1d0@bastelstu.be> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] [Under Discussion] Random Extension 4.0 From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=c3=bcsterhus?=) Hi On 2/21/22 03:57, Go Kudo wrote: > I am sorry for the delay in replying. Don't worry, there was a weekend inbetween and I totally understand that one wants to take their weekend off. > Thank you for the clear explanation. > It is true that the RFC in its current form lacks explanation. I'll try to > fix this first. Sounds good. > Also, as I look into other languages' implementations, I see the need to > add some RNGs such as PCG. I will update the RFC to include these. I suggest you avoid "feature creep" within the RFC. Additional engines can be added easily later on if the need arises. But for now it's more important to get a reliable basis that one can build onto. Having a choice of a multitude of different engine just distracts from that goal and can be confusing for the user. With xoshiro256** there's a very good choice that already is part of the RFC, no need to have something else that might or might not be slightly better in some case. Best regards Tim Düsterhus