Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124932
Precedence: bulk
MIME-Version: 1.0
References: <CAM7F2-_i58wfkdspFRGcsDLBp8eDB2aby5ENym3KpWAf+Tq6bw@mail.gmail.com>
 <89C901BF-DCEA-498E-93B0-750C49E6275B@getmailspring.com> <CAM7F2-895zXfqyDLt9C0_WYTkAAP9Q4wG86Xz6pn8xHNE2wfFw@mail.gmail.com>
 <0BB4DB2D-62E1-40F9-91F3-7D48367D2CBE@edison.tech> <CAM7F2--N28KTb3fqL=qOppMEqxiM+6Mo9d=ztQBUVfYqcWUnXA@mail.gmail.com>
 <9fb2c610-eed9-4773-8158-adef581d6a5b@free.fr> <CAM7F2-_HBv8SFrE3+Pb7afyqLXvBr2-paVrdCkpgmFi3ubn2Ww@mail.gmail.com>
In-Reply-To: <CAM7F2-_HBv8SFrE3+Pb7afyqLXvBr2-paVrdCkpgmFi3ubn2Ww@mail.gmail.com>
Date: Wed, 14 Aug 2024 22:05:36 +0300
Message-ID: <CAL0xaBFwMfAmGQ1xdxVVpJ8hXjFOzZU6ZBE4kF=0OoXZ-LAk-w@mail.gmail.com>
Subject: Re: [PHP-DEV] [DISCUSSION] C++ Enhancements in Zend API
To: Lanre <lnearwaju@gmail.com>
Cc: Pascal Chevrel <pascalc@gmail.com>, Mike Schinkel <mike@newclarity.net>, 
	John Coggeshall <john@coggeshall.org>, Levi Morrison <levi.morrison@datadoghq.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007b4fb1061fa96bf8"
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--0000000000007b4fb1061fa96bf8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I want to remind everyone on the thread that code does not only have to be
written, which is the "easy part", but it also has to be supported by
everyone into the future and chances that the original author sticks around
are not that high to do it.

The Rust thing is shitposting for the sake of shitposting and memeing on
the theme "rust solves everything" and "lets rewrite everything into Rust".
Here's a link with the reminder of the hard rules php-src and internals
have: https://github.com/php/php-src/blob/master/docs/mailinglist-rules.md
And here's the wiki page on the internals etiquette:
https://wiki.php.net/email_etiquette_for_people_new_to_php_internals

PHP has C as core and has allowed C++ for extensions. Expanding that
support is a no-brainer, especially since modern C++ has stepped up in
major ways and I don't think C sees a lot of development any more, so it
makes sense to move towards C++.
The only thing people on this thread need to agree on is the timeline for
expanding that support. I would suggest adopting a multi-year schedule
through multiple PHP versions and get that show on the road.
--=20

Arv=C4=ABds Godjuks
+371 26 851 664
arvids.godjuks@gmail.com
Telegram: @psihius https://t.me/psihius

--0000000000007b4fb1061fa96bf8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I want to remind everyone on the thread that code doe=
s not only have to be written, which is the &quot;easy part&quot;, but it a=
lso has to be supported by everyone into the future and chances that the or=
iginal author sticks around are not that high to do it.</div><div><br></div=
><div>The Rust thing is shitposting for the sake of shitposting and memeing=
 on the theme &quot;rust solves everything&quot; and &quot;lets rewrite eve=
rything into Rust&quot;.</div><div>Here&#39;s a link with the reminder of t=
he hard rules php-src and internals have:=C2=A0<a href=3D"https://github.co=
m/php/php-src/blob/master/docs/mailinglist-rules.md">https://github.com/php=
/php-src/blob/master/docs/mailinglist-rules.md</a>=C2=A0<br></div><div>And =
here&#39;s the wiki page on the internals etiquette:=C2=A0<a href=3D"https:=
//wiki.php.net/email_etiquette_for_people_new_to_php_internals">https://wik=
i.php.net/email_etiquette_for_people_new_to_php_internals</a></div><div><br=
></div><div>PHP has C as core and has allowed C++ for extensions. Expanding=
 that support is a no-brainer, especially since modern C++ has stepped up i=
n major ways and I don&#39;t think C sees a lot of development any more, so=
 it makes sense to move towards C++.</div><div>The only thing people on thi=
s thread need to agree on is the timeline for expanding that support. I wou=
ld suggest adopting a multi-year schedule through multiple PHP versions and=
 get that show on the road.<br></div><span class=3D"gmail_signature_prefix"=
>-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">=
<div><br></div>Arv=C4=ABds Godjuks<div>+371 26 851 664</div><div><a href=3D=
"mailto:arvids.godjuks@gmail.com" target=3D"_blank">arvids.godjuks@gmail.co=
m</a></div><div>Telegram: @psihius=C2=A0<a href=3D"https://t.me/psihius" ta=
rget=3D"_blank">https://t.me/psihius</a></div></div></div></div>

--0000000000007b4fb1061fa96bf8--