Re: [RFC] Add pack()/unpack() support for signed integers with specific endianness

Hi, > > 1. Base Letters Already Taken > > The point of a modifier is to modify something. That means that there > needs to be a “base letter”. The same base letters are also “taken” in > Perl and have the same definition. > > > 2. Parser Architecture Limitations > > That sounds like a simple problem to solve. When reaching one of the > “base letters” in question, look at the next character. Indeed, it is just that I'm not sure that it is worth adding modifiers support to pack and unpack as with this addition, most (if not all) cases should be covered then. > This is simply false. v/n/V/N identically exist in Perl. J is not clear > to me, and P appears to be different (but I don't do enough Perl to say > for certain). Perl and PHP share common letters, you are right. But looking at the table of each language, there are many differences. However, I may reword it as I realized that the RFC states that differences appear with specific endianness letters (and you showed that it's not true). There are many differences when we're not talking about endian specific formats actually. — Alexandre Daubois