Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124772
Precedence: bulk
MIME-Version: 1.0
References: <CAPyj-LB11wiZyHV8=7fEs=J==tDO+m+z4qRsXRroPnqXzNZvvg@mail.gmail.com>
 <ef8740b7-f865-04c7-cc5b-a0d1f8edf30c@php.net> <6cde6bb4-30cc-4838-a003-6333acbd6a3c@gmx.de>
 <e74bb864-bc73-ca9e-a5ea-01b11868968f@php.net>
In-Reply-To: <e74bb864-bc73-ca9e-a5ea-01b11868968f@php.net>
Date: Mon, 5 Aug 2024 22:42:50 +0700
Message-ID: <CAEZPtU6drB-hB9SR9zqrPEWr2PRqVuOPcmMXu7_oihxM=jyENw@mail.gmail.com>
Subject: Re: [PHP-DEV] Require C11 in PHP 8.4
To: Derick Rethans <derick@php.net>
Cc: "Christoph M. Becker" <cmbecker69@gmx.de>, Ilija Tovilo <tovilo.ilija@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000490965061ef1886e"
From: pierre.php@gmail.com (Pierre Joye)

--000000000000490965061ef1886e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 5, 2024, 10:03=E2=80=AFPM Derick Rethans <derick@php.net> wrote=
:

> Instead of having to deal with tickets, wouldn't be be easier if the
> compiler they used works with the features that we are using? That could
> instantly provide a link to the documentation saving all of us time.
>


it is significantly easier at configure time. Gcc 4.9 is (almost) fully c11
compliant (not 4.7).

As of windows, it will be dependent on the vc version used by the php minor
branch where it may be introduced.

That being said, I am not sure if the reason mentioned for using c11 in the
initial post is used in external extensions (included headers etc), but at
least on linux (or similar), an ext can be compiled with any version.

On windows, we can't, mainly for memory  management issues (alloc/realloc
or freed using different crt). It is possible but too many extensions, also
in core, cause issues.

best,
Pierre

>

--000000000000490965061ef1886e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Mon, Aug 5, 2024, 10:03=E2=80=AFPM Derick Rethans &=
lt;<a href=3D"mailto:derick@php.net">derick@php.net</a>&gt; wrote:</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">
Instead of having to deal with tickets, wouldn&#39;t be be easier if the <b=
r>
compiler they used works with the features that we are using? That could <b=
r>
instantly provide a link to the documentation saving all of us time.<br></b=
lockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto">it is significantly easier at configure time. Gcc 4.9 =
is (almost) fully c11 compliant (not 4.7).</div><div dir=3D"auto"><br></div=
><div dir=3D"auto">As of windows, it will be dependent on the vc version us=
ed by the php minor branch where it may be introduced.=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">That being=C2=A0said, I am not sure i=
f the reason mentioned for using c11 in the initial post is used in externa=
l extensions (included headers etc), but at least on linux (or similar), an=
 ext can be compiled with any version.</div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">On windows, we can&#39;t, mainly for memory=C2=A0 management=
 issues (alloc/realloc or freed using different crt). It is possible but to=
o many extensions, also in core, cause issues.</div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">best,</div><div dir=3D"auto">Pierre</div><div dir=3D=
"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>

--000000000000490965061ef1886e--