Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83627
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender)
Reply-To: <francois@php.net>
To: "'Pierre Joye'" <pierre.php@gmail.com>,
	"'Zeev Suraski'" <zeev@zend.com>
Cc: "'Anthony Ferrara'" <ircmaxell@gmail.com>,
	"'PHP internals'" <internals@lists.php.net>
Date: Tue, 24 Feb 2015 05:17:54 +0100
Message-ID: <081001d04fe8$dcbc0160$96340420$@php.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AdBP5wC84/PrnoTeQdebraI8BXknHQ==
Content-Language: fr
Subject: [PHP-DEV] Coercive Scalar Type Hints RFC - BC breaks
From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=)

Hi,

I ran the PHP core 'make test' on a basic configuration, still running a =
significant number of 8785 tests.

Note: the restrictions on numeric string conversions (leading =
chars/zeroes, trailing chars) are not simulated yet, but they shouldn't =
change the results very much.

The ruleset corresponding to the coercive RFC, as it is published today, =
globally broke 7.3% of tests. From these 7.3%, 5.3% correspond to the =
disabled conversions from null to scalar types, which will probably have =
to be reintroduced, as it was suspected. So, if we consider that these =
conversions are re-enabled, the resulting coercive ruleset breaks 1.9% =
of the tests, which is rather positive, IMO, because there is still room =
for improvements.

More details soon.

Regards

Fran=C3=A7ois