Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83439 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 10804 invoked from network); 21 Feb 2015 22:18:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Feb 2015 22:18:01 -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:33463] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/48-08895-71409E45 for ; Sat, 21 Feb 2015 17:18:01 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id BD1A34B021E; Sat, 21 Feb 2015 23:17:49 +0100 (CET) Reply-To: To: "'Pierre Joye'" , "'Zeev Suraski'" Cc: "'Anthony Ferrara'" , "'PHP internals'" References: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com> <8250289916f5128b5bc1a114428d374e@mail.gmail.com> In-Reply-To: Date: Sat, 21 Feb 2015 23:17:51 +0100 Message-ID: <063a01d04e24$3bdddf90$b3999eb0$@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: AQKcPg+jpyYspJS11b5G1A7RBHpKTgFW66vOANg4ZZICNw4QFptAl7ow Content-Language: fr X-Antivirus: avast! (VPS 150221-0, 21/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Coercive Scalar Type Hints RFC From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) Hi Pierre, I'm currently writing a patch to test the proposed ruleset, as BC is the = key point. If BC breaks are so massive that we have to revert to the original = 'weak' mode, I will be the first one to vote for dual-mode. There will be two slightly different branches : one totally disabling = (IS_LONG|IS_FLOAT|IS_STRING to bool) and one implementing the current = way of converting these (with the small modification about numeric = strings recognized as false). There may be a first level without support = for trailing blanks but it is not important as it is an extension of the = current behavior, not a restriction. More when something is ready. Regards Fran=C3=A7ois