Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86922
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.48 as permitted sender)
Message-ID: <558F43CA.8000700@gmail.com>
Date: Sat, 27 Jun 2015 17:46:02 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: NAN/INF->int conversion in 5.6
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

Working on cleaning up the spec, I've discovered that in PHP 5.6 and
below conversion of NAN to int produces unexpected result of
-9223372036854775808 (on 64-bit, 32-bit probably different). In PHP 7,
it produces expected 0. See e.g.: http://3v4l.org/RKQuu
Same weirdness is for INF and -INF which sometimes produce 0 (e.g. on my
local machine) and sometimes -9223372036854775808 - e.g.
http://3v4l.org/ivX1D

My question is: should we backport code from PHP 7 that checks for
infinity/nan and put it into 5.6? Or it's not worth it and it's ok for
5.6 to return random weird stuff there? (I know it's not exactly random
and there's a reason why it's that number but it looks that way).
-- 
Stas Malyshev
smalyshev@gmail.com