Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130038
Message-ID: <4c602fcd-5b07-4633-b816-a2bf8cb4b5de@bastelstu.be>
Date: Fri, 6 Feb 2026 21:23:56 +0100
Precedence: list
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Add pack()/unpack() endianness modifiers for
 floating-point numbers
To: Alexandre Daubois <alex.daubois+php@gmail.com>,
 PHP internals list <internals@lists.php.net>
References: <CAMU7irKOXqSs3zJfPBy7dPgGE0ycDGG89eowuUuRywET_jT02Q@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAMU7irKOXqSs3zJfPBy7dPgGE0ycDGG89eowuUuRywET_jT02Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 1/30/26 10:51, Alexandre Daubois wrote:
> Following the recent successful vote of the RFC adding the support for
> endianness modifiers on integers, I'd like to present the natural
> continuation of it. It will complete the support of endianness
> modifiers across relevant format letters of pack()/unpack().
> 
> Here is the RFC: https://wiki.php.net/rfc/pack-unpack-float-endianness-modifier

Thank you for the RFC. This sounds like a straight-forward follow-up for 
the previous RFC.

The only comment I have would be that it would make sense to list 
deprecating g, G, e, and E as a Future Scope option to further align the 
behavior with Perl, which doesn't support g, G, e, E. It is not 
necessary or expected that everything from Future Scope is done, it is 
just a list of things that would be possible as a follow-up, deferring 
figuring out the details to a later point.

Best regards
Tim Düsterhus