Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83872 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50209 invoked from network); 26 Feb 2015 08:06:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Feb 2015 08:06:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; 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:37483] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1F/50-47686-CE3DEE45 for ; Thu, 26 Feb 2015 03:06:04 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id AA3C84B0258; Thu, 26 Feb 2015 09:05:41 +0100 (CET) Reply-To: To: "'Pierre Joye'" Cc: "'Zeev Suraski'" , "'Anthony Ferrara'" , "'PHP internals'" References: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com> <8250289916f5128b5bc1a114428d374e@mail.gmail.com> <09da01d05174$cd7382e0$685a88a0$@php.net> In-Reply-To: Date: Thu, 26 Feb 2015 09:05:55 +0100 Message-ID: <0a0e01d0519b$0c9338a0$25b9a9e0$@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+jpyYspJS11b5G1A7RBHpKTgFW66vOANg4ZZIBOJUt6QIcwpl/AeIBZpMDDZr3vwHYWlMZAXMcvV8CVqfXAZrqBlPw Content-Language: fr X-Antivirus: avast! (VPS 150225-3, 25/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?=) > De : Pierre Joye [mailto:pierre.php@gmail.com] >=20 > As I said earlier, E_DEPRECATED will only caught what it sees, we miss > what it does not and actually casts happily. Sorry, Pierre, I don't see what you mean. You're probably right but I = don't understand what you mean with 'casting'. AFAIK, we are not = touching casting rules, implicit or explicit. We just take the ZPP code = and raise some E_DEPRECATED while keeping the whole logic. Can you try to explain again or give a scenario I can understand. >=20 > > And temporary because developers will quietly fix their code and = the > hidden messages will disappear. So, we probably won't have to rely on = 'good > luck'. >=20 > Again. It seems you only see issues with this insignificant > E_DEPRECATED messages, it will be just like other or E_NOTICE, they > will disable it and move on. However my point is in a totally > different area, the one we have no idea what is going on because it is > now casted while it was not before. Do you mean that adding type hints will break existing code ? If someone = can explain... We do not have data to cover these > cases. It is not a lack of will but it is simply impossible to have > for all apps out there in production (as you said before). And it is > exactly why I am against changing the casting rules, even for a single > yota beyond what we have done already (or close to this area). >=20 >=20 > > FUD apart, every test Dmitry ran using his upcoming patch (which = will > implement E_DEPRECATED) on existing PHP software raised very few new > errors. More : after analysis, all these messages except 1, I believe, > correspond to undetected bugs in the PHP code. Like the bug I detected = in > the PHP code to build phar.phar. So, I can go further : we are not = breaking > anything *and* we are helping users to find undetected bugs in their > codebase. Nice side effect, isn't it ? >=20 > Again, see my previous comment in this mail. >=20 > Cheers, > -- > Pierre >=20 > @pierrejoye | http://www.libgd.org