Re: [RFC] [VO TE] Transform exit() fro m a language construct into a standard function

From: Date: Wed, 07 Aug 2024 14:27:56 +0000
Subject: Re: [RFC] [VO TE] Transform exit() fro m a language construct into a standard function
References: 1 2  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On 7 August 2024 14:30:24 BST, Theodore Brown <[email protected]> wrote:
>On Tue, July 30, 2024 at 03:49 G. P. Banyard wrote:
>
>> Hello Internals,
>>
>> I have just opened the vote for the "Transform exit() from a language construct into a
>> standard function" RFC:
>> https://wiki.php.net/rfc/exit-as-function
>>
>> The vote will last for two weeks until the 13th of August 2024.
>
>I really appreciate RFCs like this which not only make the language more consistent for userland
>developers, but also simplify PHP's internal implementation, paving the way for future
>optimizations and new functionality.
>
>In my experience, extension developers nearly always have to make some changes to support each
>new PHP version, so I'm not sure why that would be a reason to prevent improving the language.

This is misrepresenting my concern.

I understand that new versions require changes. 

One of my issues is, is that so far I could not find a way to replicate existing functionality with
this patch applied.

The RFC does not mention a BC break, nor does it have an entry for UPGRADING.INTERNALS either.

cheers
Derick 


Thread (37 messages)

« previous php.internals (#124826) next »