Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128711
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>
In-Reply-To: <eab4a39430e842368ec54b4c56595dbb@bastelstu.be>
Date: Wed, 17 Sep 2025 09:09:46 +0200
Message-ID: <CAMU7irKebc9KDmLC57pdGyd8fQ4TdthYONUN2oBWgc=7-yt_KA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Add pack()/unpack() support for signed integers
 with specific endianness
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: 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,

> I'm not sure if =E2=80=9Call formatting codes work the same=E2=80=9D is s=
till 100%
> accurate (due to J and P), but =E2=80=9Cmany differences=E2=80=9D is defi=
nitely false.
> I'm seeing the following differences:
>
> - J and P might or might not be different.
> - e, E, g, and G don't exist in Perl (it would be d<, d>, f<, and f>
> respectively; these format specifiers could be deprecated if this RFC
> ships).
>
> Both w and W are already taken in Perl and would actually be a
> difference.

I'm not sure to exactly understand what you mean. Do you propose to
introduce < and > modifiers and deprecate some letters, if I get it
right?

=E2=80=94 Alexandre Daubois