Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77121
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <7E2B341D-F0BD-4E3A-BE41-FCD5539EC8D3@ajf.me>
References: <CAPwsocHegEcF7kQEgwjC=PbkJKq7aq8Bv_A6QAy2fPFghJ=0WQ@mail.gmail.com>
	<7E2B341D-F0BD-4E3A-BE41-FCD5539EC8D3@ajf.me>
Date: Tue, 9 Sep 2014 22:26:03 +0100
Message-ID: <CAPwsocF9nRGDuNZ7ACS7d3hi1Hj2LZnZtG9bQob-HnPPpe3eMw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] pack() and unpack() 64 bit format codes
From: leight@gmail.com (Leigh)

On 9 September 2014 21:16, Andrea Faulds <ajf@ajf.me> wrote:
>
> Why is there no big/little-endian signed long long?
>

I suppose you could argue that these count

i - signed integer (machine dependent size and byte order)
I - unsigned integer (machine dependent size and byte order)

However they specify machine dependent size, and they do not increase
to 64 bit on the average 64 bit system (sizeof(int) remains at 4 when
sizeof(long) goes to 8 on my systems). It's obviously possible to add
signed variants, so I open the floor to the usual bikeshedding on what
letters should be used, but I'd prefer to stick to translating the
32bit _specific_ behaviour to 64 bit for now, such was the goal of the
PR.