Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124827
Date: Wed, 07 Aug 2024 17:07:29 +0200
To: 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: <0FA837CD-60C3-4F4C-9044-C44FB0AF5788@php.net>
References: <WAN6ETlWt7JfcVoyeYfY_F_eLE6WzQa87F7yi8SHISmyktMYx7YcA6oG5dis3gFeI36VBjSfjGw4AT6psFFDXEUNRrvKRRn4LxfdCxFBccw=@gpb.moe> <PH7PR16MB57811CD259E8AED311F017B7DEB82@PH7PR16MB5781.namprd16.prod.outlook.com> <0FA837CD-60C3-4F4C-9044-C44FB0AF5788@php.net>
Message-ID: <32BE9C65-F955-44F0-B994-D588D851902E@heigl.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary=----SB97CHJNCOYEZE6M3PUKKDGMH54524
Content-Transfer-Encoding: 7bit
From: andreas@heigl.org (Andreas Heigl)

------SB97CHJNCOYEZE6M3PUKKDGMH54524
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

Stupid question maybe, but are we voting on the RFC or on the patch?

If the patch does not match what=2Ethe RFC proposes, then the patch has a =
problem=2E That should IMO though not affect voting on an RFC=2E

Or am I=2Emissimg something?

Cheers

Andreas





On 7 August 2024 16:27:56 CEST, Derick Rethans <derick@php=2Enet> wrote:
>On 7 August 2024 14:30:24 BST, Theodore Brown <theodorejb@outlook=2Ecom> =
wrote:
>>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 =
construct 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 imple=
mentation, paving the way for future optimizations and new functionality=2E
>>
>>In my experience, extension developers nearly always have to make some c=
hanges 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 e=
xisting functionality with this patch applied=2E
>
>The RFC does not mention a BC break, nor does it have an entry for UPGRAD=
ING=2EINTERNALS either=2E
>
>cheers
>Derick

------SB97CHJNCOYEZE6M3PUKKDGMH54524
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div dir=3D"auto">Stupid question maybe, but are w=
e voting on the RFC or on the patch?<br><br>If the patch does not match wha=
t=2Ethe RFC proposes, then the patch has a problem=2E That should IMO thoug=
h not affect voting on an RFC=2E<br><br>Or am I=2Emissimg something?<br><br=
>Cheers<br><br>Andreas<br><br><br><br></div><br><br><div class=3D"gmail_quo=
te"><div dir=3D"auto">On 7 August 2024 16:27:56 CEST, Derick Rethans &lt;de=
rick@php=2Enet&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"m=
argin: 0pt 0pt 0pt 0=2E8ex; border-left: 1px solid rgb(204, 204, 204); padd=
ing-left: 1ex;">
<pre class=3D"k9mail"><div dir=3D"auto">On 7 August 2024 14:30:24 BST, The=
odore Brown &lt;theodorejb@outlook=2Ecom&gt; wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin: 0pt 0pt 1ex 0=2E8ex; border-left: 1px =
solid #729fcf; padding-left: 1ex;"><div dir=3D"auto">On Tue, July 30, 2024 =
at 03:49 G=2E P=2E Banyard wrote:<br><br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin: 0pt 0pt 1ex 0=2E8ex; border-left: 1px solid #ad7fa8;=
 padding-left: 1ex;"><div dir=3D"auto"> Hello Internals,<br><br> I have jus=
t opened the vote for the "Transform exit() from a language construct into =
a standard function" RFC:<br> <a href=3D"https://wiki=2Ephp=2Enet/rfc/exit-=
as-function">https://wiki=2Ephp=2Enet/rfc/exit-as-function</a><br><br> The =
vote will last for two weeks until the 13th of August 2024=2E<br></div></bl=
ockquote><div dir=3D"auto"><br>I really appreciate RFCs like this which not=
 only make the language more consistent for userland developers, but also s=
implify PHP's internal implementation, paving the way for future optimizati=
ons and new functionality=2E<br><br>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=
=2E<br></div></blockquote><div dir=3D"auto"><br>This is misrepresenting my =
concern=2E<br><br>I understand that new versions require changes=2E <br><br=
>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<br><br>The RFC does not men=
tion a BC break, nor does it have an entry for UPGRADING=2EINTERNALS either=
=2E<br><br>cheers<br>Derick<br></div></pre></blockquote></div></body></html=
>
------SB97CHJNCOYEZE6M3PUKKDGMH54524--