Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117135 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 30755 invoked from network); 24 Feb 2022 07:58:37 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 Feb 2022 07:58:37 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 75B0518053B for ; Thu, 24 Feb 2022 01:18:33 -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 ; Thu, 24 Feb 2022 01:18:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1645694311; bh=ROcgGgLjXt4gk24OxrRpB5j4hMrqWNsQ/OkkdOfTfyw=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=FYkj2NoOYzivbqBNKYI339FuZiqMR4vTFCA+tTxlRE8c7VYZKCR0g3fhvtYM2//m3 dEAQf4+xm2he0K5vCDwpF6AxvmBO4xs/p1HtdmacXwyXsRhLaRodM2I8UKN5GAHm+a HpVwOCHPal5b+tTPBCQnWRSaehl5lGiGgMOIq2EF0if+AwSmIkmekNYckhixkwPrw/ AxMMekqc1EVUqh2z7/NNwQ2786uLevC3yn2IpvVUtJz1y+7DeJFGEKbov5OeYmco7r QP2IzTpTD1fF4pEq0O0U8GYITMs+QIXxWQy4GzGODNXngN0tBUu99WjKhT9x7v45ho UkEpmKnQpl1SQ== Message-ID: <7e1fb83c-adfc-f377-3f45-cd9855c42c00@bastelstu.be> Date: Thu, 24 Feb 2022 10:18:29 +0100 MIME-Version: 1.0 Content-Language: en-US To: Go Kudo Cc: internals@lists.php.net References: <2c667812-88c8-0b7b-3558-561a1348d0b2@bastelstu.be> <5f496cf9-8754-b009-9cb5-b978222b2249@bastelstu.be> <26a8c3ee-9f0a-793c-10c0-7e642eedf1d0@bastelstu.be> <47cb96f5-4450-0377-dc95-67faac3fef33@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/24/22 09:47, Go Kudo wrote: > RFC has been updated. Is this up to the required standard? > https://wiki.php.net/rfc/rng_extension I've just passed my own RFC just yesterday, so I'm certainly not an expert with regard to RFC standards, however: I think the explanation in the RFC is *much* better now. It explains all the important aspects, so that one does not need to look into the implementation to understand how it is supposed to work. However it would benefit from a little more structuring. I suggest to add some additional sub-headings to the "Proposal" section. Perhaps something like this: # Proposal ## Current Issues ### Global State ### Mersenne Twister is not state of the art ## Random Engine ### MT ### xorshift ### xoshiro ### ## Randomizer I'm not sure whether all those headlines make sense, you're the expert here. > I acknowledge that the previous RFC may have been difficult to discuss. If > the problem has been solved, I would like to make another ML-wide > announcement and wait for two weeks from there. I would advice you not to rush the vote. Take your time to make the RFC perfect. It does not help if you start the vote in 2 weeks and then the RFC is declined, because of some issues. Best regards Tim Düsterhus