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

From: Date: Wed, 07 Aug 2024 20:33:14 +0000
Subject: Re: [RFC] [VOTE] Transform exit() from a language construct into a standard function
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On Wed, August 7, 2024 at 08:27 Derick Rethans wrote:

> On 7 August 2024 14:30:24 BST, Theodore Brown wrote:
>> 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.

Hi Derick,

I'm confused by this, since earlier in the thread Tim responded with examples showing how the
behavior of exit() can still be observed and correctly handled. If that didn't address your
issue, can you explain it further? It seems like right now everyone is left bewildered about what
functionality you couldn't replicate.

Kind regards,
Theodore


Thread (37 messages)

« previous php.internals (#124829) next »