Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81718
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <3B265E0A-7479-456A-B134-5CA607C68EFF@ajf.me>
References: <CAPwsocEjjJPkUvihYdj8tNRrf3XQ9WJzT=1Er6gjLs2MMgHwsw@mail.gmail.com>
	<1D8DC03D-0E2C-494C-9ED2-244334F57D8A@ajf.me>
	<CAPwsocHACBzYg8L5O3s2r=BGDrhe4VaLNTFmCX=rz_4_rpRFZw@mail.gmail.com>
	<6E8210CD-4BA3-4694-8482-4803F562D77C@ajf.me>
	<CAPwsocFgHY3B-0dt6QWSmLJOgEvcBwtE1rSHXWrRh44jAv_u0w@mail.gmail.com>
	<1BEEF374-D8BC-4FE2-8CE0-5EBB1AC4CF04@ajf.me>
	<CAPwsocFQgZy9WDGjG6PQ+mUvwYkzS69n0s-Uw5yCYveGK1OYZQ@mail.gmail.com>
	<3B265E0A-7479-456A-B134-5CA607C68EFF@ajf.me>
Date: Tue, 3 Feb 2015 14:59:15 +0000
Message-ID: <CAPwsocFiDA3jj=Q3Vzd9a==48+G6ygTt_4QJU6jqi+iCQmyV8g@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Zero-fill right shift.
From: leight@gmail.com (Leigh)

On 3 February 2015 at 14:49, Andrea Faulds <ajf@ajf.me> wrote:
> It=E2=80=99s not =E2=80=9Cbroken=E2=80=9D, the behaviour is just differen=
t to account for it now being an arbitrary-precision type.
>

That's pretty much the definition of a BC issue.

> Also, the bigint changes only affect you if you=E2=80=99re dealing with l=
arge integers anyway. If you want to preserve the horrid float promotion be=
haviour, you can do so explicitly. But I think in most cases, it=E2=80=99s =
better to trade off performance for lack of data loss.
>

It's not anything to do with float promotion or data loss. If I'm
working with a 64-bit bitmask that gets promoted to bigint when I set
the high bit, it's a performance regression from then on. Not
everything written in PHP is a web app.