Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107777
MIME-Version: 1.0
References: <A91E718E-B023-42DC-AC8D-BC989F5A80E4@cschneid.com>
 <CAF+90c_75x0ZoD63CoLXY3kUKNQQuR_HhaO998osHuzV7ZGXuw@mail.gmail.com>
 <CAEKnhAHbUf0w1WYqHWYAQD79DJo21HFC1cYoo07AV12NhpBAQQ@mail.gmail.com>
 <CAEKnhAHmmj+iySEPsuT9McJXKb9sR8MOTinvsxQYakDn2_hAMw@mail.gmail.com> <CAEKnhAFn1ivFPPNM0q6bsPRCekp2AaDNfUNkwrL8csaPgECcJA@mail.gmail.com>
In-Reply-To: <CAEKnhAFn1ivFPPNM0q6bsPRCekp2AaDNfUNkwrL8csaPgECcJA@mail.gmail.com>
Date: Thu, 7 Nov 2019 10:00:56 +0000
Message-ID: <CALKiJKpHr3iiGMMoadR-=kMX04PaXihNVF5n2_oKqGj69u4YNg@mail.gmail.com>
To: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000086a6920596bebedc"
Subject: Re: [PHP-DEV] PHP 7.4 BC break with openssl_random_pseudo_bytes()
From: rowan.collins@gmail.com (Rowan Tommins)

--00000000000086a6920596bebedc
Content-Type: text/plain; charset="UTF-8"

On Wed, 6 Nov 2019 at 19:44, Jakub Zelenka <bukka@php.net> wrote:

> I have to say that the RFC wasn't really well done as the implementation
> followed which caused this omission. We should really look properly to the
> implementation when creating RFC so it's more detailed and doesn't cause
> omission like this.
>


There's a bit of a Catch-22 there: voters want to know all the edge-cases
before they approve an RFC; but developers want to know the RFC will be
approved before they spend hours refining a patch. In some ways, it would
be good to have two votes: one on the principle, and one on the detailed
implementation; but that could make the process feel quite long and
bureaucratic.

Regards,
-- 
Rowan Tommins
[IMSoP]

--00000000000086a6920596bebedc--