Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129055
Precedence: list
MIME-Version: 1.0
Date: Mon, 03 Nov 2025 17:19:54 +0100
To: Alexandre Daubois <alex.daubois+php@gmail.com>
Cc: PHP internals list <internals@lists.php.net>
Subject: Re: [PHP-DEV] Re: [RFC] Add pack()/unpack() support for signed
 integers with specific endianness
In-Reply-To: <CAMU7irLUBcRrXk9mmGK2TB6uCiviY+Qmxi16gfy33ZbpZKvJKw@mail.gmail.com>
References: <CAMU7irLuV_CWR37odtuu0TL7io_bONy+5xebY82YnVb38RtEzg@mail.gmail.com>
 <CAMU7irLP0LHZzzkgXywBjp_Gp1_2rHY-erg85y4ahStOoWZZTQ@mail.gmail.com>
 <86c27cd68c8ba8056d832a845eb15dcd@bastelstu.be>
 <CAMU7irLUBcRrXk9mmGK2TB6uCiviY+Qmxi16gfy33ZbpZKvJKw@mail.gmail.com>
Message-ID: <b2539b6a7a2d58fdb5b6cfa0c90b037c@bastelstu.be>
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

Am 2025-10-31 14:27, schrieb Alexandre Daubois:
> I reworked the wording a bit and labeled the implementation as
> "proposed PR" instead of "current PR" to reduce potential confusion.

This is not resolving the factual issues with the RFC. The “Why Perl's 
Approach Is Not The Best Fit For PHP” section still contains the 
incorrect statements that I previously pointed out in my email on 
September 16th: https://news-web.php.net/php.internals/128705. With 
regard to "(2) Parser Architecture Limitations" specifically, please see 
my previous reply to Gina.

With regard to the “Considered Alternatives”, it is also not clear to me 
what “complex migration path” there should be. Supporting specific 
endianess for signed integers is a new feature. There is no migration 
path.

Best regards
Tim Düsterhus