Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128731
Precedence: list
MIME-Version: 1.0
References: <CAMU7irLuV_CWR37odtuu0TL7io_bONy+5xebY82YnVb38RtEzg@mail.gmail.com>
 <e019e5c8feccbb4586153d7d93db2aec@bastelstu.be> <CAMU7irKbh-1ExY0sUsM8m5npKe_bcVYPcr62DG+M7C2vP2eNmw@mail.gmail.com>
 <eab4a39430e842368ec54b4c56595dbb@bastelstu.be> <CAMU7irKebc9KDmLC57pdGyd8fQ4TdthYONUN2oBWgc=7-yt_KA@mail.gmail.com>
 <327029177342d39a2a29051c3f28062b@bastelstu.be> <CAMU7ir+4x3UPobGS3SFQ5PhoXD-oh4-Nz5B_vuqc1qDeb4QRqg@mail.gmail.com>
 <dc2a2fc7-8c84-473f-b56c-62e4821617a7@app.fastmail.com>
In-Reply-To: <dc2a2fc7-8c84-473f-b56c-62e4821617a7@app.fastmail.com>
Date: Fri, 26 Sep 2025 09:17:24 +0200
Message-ID: <CAMU7irLoxq7EN70sx91V7MmoHu07nnYPF81F=8tWh-9zqn2arg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Add pack()/unpack() support for signed integers
 with specific endianness
To: Rob Landers <rob@bottled.codes>
Cc: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>, 
	PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: alex.daubois+php@gmail.com (Alexandre Daubois)

Hi Rob,

> It will make it hard or impossible to justify adding something to PHP tha=
t isn=E2=80=99t in Perl. The fact that they=E2=80=99re different is a boon =
and a curse. That being said, nobody has really changed this or proposed an=
ything PHP specific in a long time.

That's right. However, if I'm correct, the proposed change in this RFC
_should_ be the last addition as all types of data and endianness
should be supported. But I get your point indeed, it would set a
"legal precedent" on something that may not need one.

> Which begs the question, what will be the next version of PHP? 9.0 or 8.6=
?

The next version is likely to be 8.6. The 8.5 branch has been cut this
week and the NEWS file now targets 8.6 on master when we (up)merge
changes.

=E2=80=94 Alexandre Daubois