Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124826
Date: Wed, 07 Aug 2024 15:27:56 +0100
To: internals@lists.php.net, Theodore Brown <theodorejb@outlook.com>,
 "Gina P. Banyard" <internals@gpb.moe>,
 PHP internals <internals@lists.php.net>
Subject: =?US-ASCII?Q?Re=3A_=5BPHP-DEV=5D_=5BRFC=5D_=5BVO?=
 =?US-ASCII?Q?TE=5D_Transform_exit=28=29_fro?=
 =?US-ASCII?Q?m_a_language_construct_into_a_standard_function?=
User-Agent: K-9 Mail for Android
In-Reply-To: <PH7PR16MB57811CD259E8AED311F017B7DEB82@PH7PR16MB5781.namprd16.prod.outlook.com>
References: <WAN6ETlWt7JfcVoyeYfY_F_eLE6WzQa87F7yi8SHISmyktMYx7YcA6oG5dis3gFeI36VBjSfjGw4AT6psFFDXEUNRrvKRRn4LxfdCxFBccw=@gpb.moe> <PH7PR16MB57811CD259E8AED311F017B7DEB82@PH7PR16MB5781.namprd16.prod.outlook.com>
Message-ID: <0FA837CD-60C3-4F4C-9044-C44FB0AF5788@php.net>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: derick@php.net (Derick Rethans)

On 7 August 2024 14:30:24 BST, Theodore Brown <theodorejb@outlook=2Ecom> wr=
ote:
>On Tue, July 30, 2024 at 03:49 G=2E P=2E Banyard wrote:
>
>> Hello Internals,
>>
>> I have just opened the vote for the "Transform exit() from a language c=
onstruct into a standard function" RFC:
>> https://wiki=2Ephp=2Enet/rfc/exit-as-function
>>
>> The vote will last for two weeks until the 13th of August 2024=2E
>
>I really appreciate RFCs like this which not only make the language more =
consistent for userland developers, but also simplify PHP's internal implem=
entation, paving the way for future optimizations and new functionality=2E
>
>In my experience, extension developers nearly always have to make some ch=
anges to support each new PHP version, so I'm not sure why that would be a =
reason to prevent improving the language=2E

This is misrepresenting my concern=2E

I understand that new versions require changes=2E=20

One of my issues is, is that so far I could not find a way to replicate ex=
isting functionality with this patch applied=2E

The RFC does not mention a BC break, nor does it have an entry for UPGRADI=
NG=2EINTERNALS either=2E

cheers
Derick