Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128703
Feedback-ID: ifab94697:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Tue, 16 Sep 2025 15:27:08 +0200
To: internals@lists.php.net
Message-ID: <694fd998-43a2-4c6b-828c-aa1feb81d424@app.fastmail.com>
In-Reply-To: 
 <CAMU7irLuV_CWR37odtuu0TL7io_bONy+5xebY82YnVb38RtEzg@mail.gmail.com>
References: 
 <CAMU7irLuV_CWR37odtuu0TL7io_bONy+5xebY82YnVb38RtEzg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Add pack()/unpack() support for signed integers with
 specific endianness
Content-Type: multipart/alternative;
 boundary=53c46cfcc82645c49153c8efe5dab727
From: rob@bottled.codes ("Rob Landers")

--53c46cfcc82645c49153c8efe5dab727
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 16, 2025, at 13:45, Alexandre Daubois wrote:
> Hello Internals,
>=20
>=20
> I=E2=80=99d like to present this new RFC. When discussing the issue, w=
e first thought that the RFC process wasn=E2=80=99t necessary. However, =
discussions on the PR showed that selecting new letters for pack and unp=
ack is more challenging than we initially thought, thus creating an RFC =
for this change.
>=20
> Here is the link to the RFC: https://wiki.php.net/rfc/pack-unpack-endi=
anness-signed-integers-support
>=20
> Best,
> Alexandre Daubois

Hi Alexandre,

Thank you for your work on this. Of all the RFCs I've seen in awhile, th=
is one is one that I'm most excited to see after writing a protobuf impl=
ementation.=20

If there is one thing I would be over the moon for, it would be for also=
 adding zigzag encoding as a possible signed integer encoding (maybe usi=
ng Z/z as the letter)? It is more efficient for signed integers (vs. two=
s-complement) where a variable length integer is desired. I can understa=
nd if this is out of scope, but I thought I'd ask.

=E2=80=94 Rob
--53c46cfcc82645c49153c8efe5dab727
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div>On Tue, Sep =
16, 2025, at 13:45, Alexandre Daubois wrote:</div><blockquote type=3D"ci=
te" id=3D"qt" style=3D""><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"a=
uto"><div>Hello Internals,</div><div id=3D"qt-m_1246795834018143218m_717=
4776667377421182AppleMailSignature" dir=3D"ltr"><br></div><div><br></div=
><div>I=E2=80=99d like to present this new RFC. When discussing the issu=
e, we first thought that the RFC process wasn=E2=80=99t necessary. Howev=
er, discussions on the PR showed that selecting new letters for pack and=
 unpack is more challenging than we initially thought, thus creating an =
RFC for this change.</div><div><br></div><div>Here is the link to the RF=
C:&nbsp;<a href=3D"https://wiki.php.net/rfc/pack-unpack-endianness-signe=
d-integers-support" target=3D"_blank">https://wiki.php.net/rfc/pack-unpa=
ck-endianness-signed-integers-support</a></div><div><br></div><div>Best,=
</div><div>Alexandre Daubois</div></div></div></div></blockquote><div><b=
r></div><div>Hi Alexandre,</div><div><br></div><div>Thank you for your w=
ork on this. Of all the RFCs I've seen in awhile, this one is one that I=
'm most excited to see after writing a protobuf implementation. </div><d=
iv><br></div><div>If there is one thing I would be over the moon for, it=
 would be for also adding zigzag encoding as a possible signed integer e=
ncoding (maybe using Z/z as the letter)? It is more efficient for signed=
 integers (vs. twos-complement) where a variable length integer is desir=
ed. I can understand if this is out of scope, but I thought I'd ask.<br>=
</div><div><br></div><div id=3D"sig121229152">=E2=80=94 Rob</div></body>=
</html>
--53c46cfcc82645c49153c8efe5dab727--