On 3 February 2015 at 14:49, Andrea Faulds <a...@ajf.me> wrote:
> It’s not “broken”, the behaviour is just different 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’re dealing with large 
> integers anyway. If you want to preserve the horrid float promotion 
> behaviour, you can do so explicitly. But I think in most cases, it’s 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.

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to