Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83542
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: "'Zeev Suraski'" <zeev@zend.com>,
	"'PHP internals'" <internals@lists.php.net>
References: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com>
In-Reply-To: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com>
Date: Mon, 23 Feb 2015 06:05:18 +0100
Message-ID: <06d801d04f26$51560d90$f40228b0$@php.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQKcPg+jpyYspJS11b5G1A7RBHpKTptlvVEQ
Content-Language: fr
Subject: RE: [PHP-DEV] Coercive Scalar Type Hints RFC
From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=)

Hi,

For those interested in evaluating the impact of ZPP ruleset modications =
on internal and userland code, A pull request is now available :

https://github.com/php/php-src/pull/1110

Please note that this is not a mere implementation of the RFC ruleset, =
although it comes preconfigured this way. It contains a set of 12 =
configurable options, each one enabling/disabling a particular ruleset =
modification. This allows for a much more powerful exploration of =
potential modifications and BC breaks against the existing codebase. =
Every combination of individual behaviors is possible, providing a =
theoretical number of about 3,000 potentials rulesets. Of course, a lot =
of these are not consistent, but it still allows for creative thinking.

Given the time I had to write it, I didn't perform extensive testing. I =
just ensured the ruleset described in the RFC and the one you get when =
activating every possible changes both compile and seem to work as =
expected. I'll test more cases tomorrow. So, code review is key priority =
and every error (compile or runtime) you may get should be reported as =
fast as possible.

Overall configuration possibilities include and go beyond the STH RFC, =
with the exception of numeric strings, whose proposed restrictions are =
not implemented yet, but will be soon.

So, I hope you'll enjoy the new toy. And thoughts are welcome, as usual.

Regards

Fran=C3=A7ois