Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129427
Precedence: list
MIME-Version: 1.0
References: <CAMU7irLuV_CWR37odtuu0TL7io_bONy+5xebY82YnVb38RtEzg@mail.gmail.com>
 <CAMU7ir+0r1c86Z1YcHSLts15Nv2iQnHxcT1AO6K1FVt8PJDDLA@mail.gmail.com>
 <9b6665e9-7daa-4138-9e4d-180425cc7c8c@bastelstu.be> <d1f8b328-eb35-47e4-b6c9-fa1ca970f64a@mabe.berlin>
In-Reply-To: <d1f8b328-eb35-47e4-b6c9-fa1ca970f64a@mabe.berlin>
Date: Mon, 24 Nov 2025 12:27:02 +0100
Message-ID: <CAMU7ir+SpHVZ7NAEJ7FaY5U86U2iCKmp6rEptYgYdxaqzG7_fA@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC] Add pack()/unpack() support for signed
 integers with specific endianness
To: "Marc B." <marc@mabe.berlin>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: alex.daubois+php@gmail.com (Alexandre Daubois)

Hello Marc,

Le dim. 23 nov. 2025 =C3=A0 18:04, Marc B. <marc@mabe.berlin> a =C3=A9crit =
:

> Quoting the docs from Perl, it's also supported to use <> modifiers on fl=
oating point values but I haven't found any note about it in your RFC. In m=
y opinion it makes sense to allow these modifiers on fd as well for the sam=
e reasons as QLS.

Thanks for this information! I think that it would make sense. I added
this to the future scope section of the RFC.

While I'm eager to go deeper into the floating points topic with
pack/unpack, I feel that it would deserve a follow-up RFC so this one
doesn't grow too much. This one's focus on integers as its title and
URL suggest, but the core feature is actually adding support for
modifiers now. In the scenario of this one being accepted, we would
have plenty of time to create a follow-up and implement it (especially
since modifiers would have already been accepted).

=E2=80=94 Alexandre Daubois