Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129670
Precedence: list
MIME-Version: 1.0
Date: Mon, 22 Dec 2025 11:13:00 +0100
Message-ID: <CAOV5rgaWLQqYL76xc3VjCqA6PywFaFR47SLiPmr7ps+VMEFgcg@mail.gmail.com>
Subject: [PHP-DEV] Backed Enum and serialization
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ba9072064687acb9"
From: nyamsprod@gmail.com (ignace nyamagana butera)

--000000000000ba9072064687acb9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi all,
recently through M=C3=A1t=C3=A9, I discovered that Backed Enum behaviour wa=
s changed
for http_build_query in PHP8.4 see the github PR
https://github.com/php/php-src/issues/15650
This change was never discussed on the mailing list and seems to have been
prompt to align with a SOAP client serialization fix and to align with how
BackedEnum are serialized
using json_encode.

Now I believe the PHP does some serialization elsewhere for instance when
using fputcsv. My question is should Backed Enum also be handled
differently in case of fputcsv ?

IMHO if we want consistency in the PHP language the answer should be yes
and have BackedEnum converted to their value (string
or int) before serialization. Either way I believe a discussion about it
should take place. My goal would be to have a clear rule on how Backed Enum
is serialized across PHP regardless
of the feature. I have not made any attempt at screening or searching for
all serialization mechanisms in PHP but I presume they should all be listed
and updated to follow the same rule
for consistency.

Best regards,
Ignace

--000000000000ba9072064687acb9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div>recently through M=C3=A1t=C3=A9, I discovered =
that Backed Enum behaviour was changed for http_build_query in PHP8.4 see t=
he github PR=C2=A0<a href=3D"https://github.com/php/php-src/issues/15650">h=
ttps://github.com/php/php-src/issues/15650</a></div><div>This change was ne=
ver discussed on the mailing list and seems to have been prompt to align wi=
th a SOAP client serialization fix and to align with how BackedEnum are ser=
ialized</div><div>using json_encode.</div><div><br></div><div>Now I believe=
 the PHP does some serialization elsewhere for instance when using fputcsv.=
 My question is should Backed Enum also be handled differently in case of f=
putcsv ?</div><div><br></div><div>IMHO if we want=C2=A0consistency in the P=
HP language the answer should be yes and have BackedEnum converted to their=
 value (string</div><div>or int) before serialization. Either way I believe=
 a discussion about it should take place. My goal would be=C2=A0to have a c=
lear rule on how=C2=A0Backed Enum is serialized across=C2=A0PHP regardless<=
/div><div>of the feature. I have not made any attempt at screening or searc=
hing for all serialization mechanisms in PHP but I presume they should all =
be listed and updated to follow the same rule</div><div>for consistency.</d=
iv><div><br></div><div>Best regards,</div><div>Ignace</div></div>

--000000000000ba9072064687acb9--