Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128723
Feedback-ID: ifab94697:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Wed, 24 Sep 2025 23:45:21 +0200
To: "Alexandre Daubois" <alex.daubois+php@gmail.com>,
 =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: "PHP internals list" <internals@lists.php.net>
Message-ID: <dc2a2fc7-8c84-473f-b56c-62e4821617a7@app.fastmail.com>
In-Reply-To: 
 <CAMU7ir+4x3UPobGS3SFQ5PhoXD-oh4-Nz5B_vuqc1qDeb4QRqg@mail.gmail.com>
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>
Subject: Re: [PHP-DEV] [RFC] Add pack()/unpack() support for signed integers with
 specific endianness
Content-Type: multipart/alternative;
 boundary=f9dff0034f64461191cc20c76ad09c33
From: rob@bottled.codes ("Rob Landers")

--f9dff0034f64461191cc20c76ad09c33
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Wed, Sep 24, 2025, at 09:28, Alexandre Daubois wrote:
> Hi,
>=20
> > I'm proposing to introduce the `<` and `>` modifiers, following Perl=
's
> > lead. This would then allow to deprecate e, E, g, and G in a future
> > version and if / when that happens, PHP would be in sync with Perl
> > again. I'm not proposing that the deprecation should happen at the s=
ame
> > time, because folks should have at least one PHP version to migrate
> > where the new logic is available, but the old is not yet deprecated.
>=20
> That would be an interesting addition. Given that only those 4 have
> diverged from Perl, that could be great to sync them again. Let's wait
> for other inputs to see if someone agrees with the idea before
> potentially revamping the RFC. I personally like it.
>=20
> =E2=80=94 Alexandre Daubois
>=20

Hi,

I like the idea of following Perl, but also I have some concerns:
 1. It will make it hard or impossible to justify adding something to PH=
P that 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 anything PHP specific in a long time.=20
 2. This is a pretty breaking change, so will it have to land in PHP 9.0
 3. Which begs the question, what will be the next version of PHP? 9.0 o=
r 8.6?

=E2=80=94 Rob
--f9dff0034f64461191cc20c76ad09c33
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div><br></div><d=
iv><br></div><div>On Wed, Sep 24, 2025, at 09:28, Alexandre Daubois wrot=
e:</div><blockquote type=3D"cite" id=3D"qt" style=3D""><div>Hi,</div><di=
v><br></div><div>&gt; I'm proposing to introduce the `&lt;` and `&gt;` m=
odifiers, following Perl's</div><div>&gt; lead. This would then allow to=
 deprecate e, E, g, and G in a future</div><div>&gt; version and if / wh=
en that happens, PHP would be in sync with Perl</div><div>&gt; again. I'=
m not proposing that the deprecation should happen at the same</div><div=
>&gt; time, because folks should have at least one PHP version to migrat=
e</div><div>&gt; where the new logic is available, but the old is not ye=
t deprecated.</div><div><br></div><div>That would be an interesting addi=
tion. Given that only those 4 have</div><div>diverged from Perl, that co=
uld be great to sync them again. Let's wait</div><div>for other inputs t=
o see if someone agrees with the idea before</div><div>potentially revam=
ping the RFC. I personally like it.</div><div><br></div><div>=E2=80=94 A=
lexandre Daubois</div><div><br></div></blockquote><div><br></div><div>Hi=
,</div><div><br></div><div>I like the idea of following Perl, but also I=
 have some concerns:<br></div><ol><li>It will make it hard or impossible=
 to justify adding something to PHP that 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 anything PHP specific in a lo=
ng time.&nbsp;</li><li>This is a pretty breaking change, so will it have=
 to land in PHP 9.0</li><li>Which begs the question, what will be the ne=
xt version of PHP? 9.0 or 8.6?</li></ol><div><br></div><div id=3D"sig121=
229152">=E2=80=94 Rob</div></body></html>
--f9dff0034f64461191cc20c76ad09c33--