Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83568 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54505 invoked from network); 23 Feb 2015 13:15:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Feb 2015 13:15:02 -0000 Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:55873] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C2/8F-01128-4D72BE45 for ; Mon, 23 Feb 2015 08:15:01 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id A681B4B0277 for ; Mon, 23 Feb 2015 14:14:46 +0100 (CET) Reply-To: To: Date: Mon, 23 Feb 2015 14:14:55 +0100 Message-ID: <073a01d04f6a$b74b7dd0$25e27970$@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdBPaq4y2fqvUIexRfq2wWfhdOibnw== Content-Language: fr X-Antivirus: avast! (VPS 150223-0, 23/02/2015), Outbound message X-Antivirus-Status: Clean Subject: [PHP-DEV] Coercive Scalar Type Hints RFC - Test PR From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) Hi, As I fear this post went unnoticed by many potentially interested, I = post it in a new thread. 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