[PHP-DEV] Updates needed to various RFCs

L.S., I'm currently going through the RFC wiki page and I'm seeing various (PHP 8.4) RFCs which haven't been properly updated after the vote. I'm specifically referring to the updates which are expected to be made to an RFC as listed in point 7 and 8 in the "RFC How to" [1]. Typical example

Re: [PHP-DEV] [RFC] [VOTE] Transform exit() from a language construct into a standard function

On Friday, 9 August 2024 at 16:03, Larry Garfield wrote: > How exactly would voters veto an implementation if not through the RFC? > That's literally the only formal input mechanism they have, and previous > attempts to add others have been soundly rejected. > > As a historical note, the parti

Re: [PHP-DEV] Re: [VOTE] Static class

On 10/08/2024 23:32, Nick Lockheart wrote: Voting has now concluded for static class. The first vote cast was for, and of the first four votes cast, three were for and one was against. As the votes continued to roll in, however, it was clear which direction the wind was blowing. The final tally r

Re: [PHP-DEV] Re: [VOTE] Static class

> Voting has now concluded for static class. The first vote cast was > for, and of the first four votes cast, three were for and one was > against. As the votes continued to roll in, however, it was clear > which direction the wind was blowing. The final tally reached the the > 2/3 critical mass

[PHP-DEV] Re: [VOTE] Static class

On 15/07/2024 09:28, Bilge wrote: Hi Internals! I am pleased to announce my RFC: /Static class/ is now open for voting: The voting will run for just shy of 4 weeks to allow extra time during this busy period prior to code freeze. Kind regards, Bilge

Re: [PHP-DEV] [Vote] Asymmetric visibility v2

On Fri, Jul 26, 2024, at 1:25 PM, Larry Garfield wrote: > Voting for Asymmetric Visibility is now open. > > https://wiki.php.net/rfc/asymmetric-visibility-v2 > > The vote will end on 9 February, probably afternoonish in my timezone. I have now closed the vote on this RFC. The final result is 24 Y

[PHP-DEV] PDO_Firebird: use C++?

Hi all, a week ago Denis Simonov submitted a PR[1] regarding formatting of the new time zone types of Firebird 4.0 (which appears sensible per se). This requires to access new Firebird APIs which are written in C++ (the old Interbase APIs are still provided as C code). Now the Firebird developers

Re: [PHP-DEV] Require C11 in PHP 8.4

On 01.08.2024 at 23:57, Ilija Tovilo wrote: > Hence, it seems like it would be ok to bump our C compiler requirement > to C11. We'd like to make this change before beta 1 if there are no > objections. There are no immediate plans to make non-optional use of > other C11 features, although that is c