Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83629 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96355 invoked from network); 24 Feb 2015 05:01:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Feb 2015 05:01:21 -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:15457] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 34/00-29197-A950CE45 for ; Tue, 24 Feb 2015 00:01:15 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id D80BD4B0143; Tue, 24 Feb 2015 06:00:57 +0100 (CET) Reply-To: To: "'Yasuo Ohgaki'" Cc: "'Pierre Joye'" , "'Zeev Suraski'" , "'Anthony Ferrara'" , "'PHP internals'" References: <081001d04fe8$dcbc0160$96340420$@php.net> In-Reply-To: Date: Tue, 24 Feb 2015 06:01:07 +0100 Message-ID: <081901d04fee$e6de8d60$b49ba820$@php.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_081A_01D04FF7.48A4A310" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJ74oXxmOVhQl9Zr86VtmzdwQ7CVQLTGD0bm5F+WUA= Content-Language: fr X-Antivirus: avast! (VPS 150223-1, 23/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Coercive Scalar Type Hints RFC - BC breaks From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) ------=_NextPart_000_081A_01D04FF7.48A4A310 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I don=E2=80=99t understand which E_DEPRECATED you=E2=80=99re talking = about. The E_DEPRECATED mechanism proposed in the RFC is not implemented = yet. But, yes, all these failures will raise E_DEPRECATED, as none of = them appears in PHP 5. In such a case, hiding E_DEPRECATED will remove = every failure. =20 Regards =20 Fran=C3=A7ois =20 De : yohgaki@gmail.com [mailto:yohgaki@gmail.com] De la part de Yasuo = Ohgaki Envoy=C3=A9 : mardi 24 f=C3=A9vrier 2015 05:32 =C3=80 : francois Cc : Pierre Joye; Zeev Suraski; Anthony Ferrara; PHP internals Objet : Re: [PHP-DEV] Coercive Scalar Type Hints RFC - BC breaks =20 Hi Francois, =20 On Tue, Feb 24, 2015 at 1:17 PM, Fran=C3=A7ois Laupretre = wrote: 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. I'm guessing most failures are due to E_DEPRECATED. I suggest to test without E_DEPRECATED, then it would be fair figure for the patch. Could you run test without E_DEPRECATED? We can use -c option for almost all tests, I think. =20 Regards, -- Yasuo Ohgaki=20 yohgaki@ohgaki.net =20 ------=_NextPart_000_081A_01D04FF7.48A4A310--