Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83950 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39454 invoked from network); 27 Feb 2015 01:41:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Feb 2015 01:41:23 -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:47417] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F9/AA-32582-24BCFE45 for ; Thu, 26 Feb 2015 20:41:22 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 320104B008C; Fri, 27 Feb 2015 02:40:59 +0100 (CET) Reply-To: To: "'Anthony Ferrara'" , "'Zeev Suraski'" Cc: References: <3d639901ae85227b219e7ee59b3140fe@mail.gmail.com> <42bc7c079a67fe1aa982b5c55ecc2f16@mail.gmail.com> In-Reply-To: Date: Fri, 27 Feb 2015 02:41:15 +0100 Message-ID: <0aca01d0522e$79c08de0$6d41a9a0$@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: AQGwbbdURx2shUG2o7Zj2Ywptu8MnAHNhHseASj3TG8CBU/YnAHY8IsNAn8zUX0BDEv+qAJWJD9/AgdVbcOczZGHkA== Content-Language: fr X-Antivirus: avast! (VPS 150226-1, 26/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] A different user perspective on scalar type declarations From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : Anthony Ferrara [mailto:ircmaxell@gmail.com] =20 > They run without triggering E_DEPRECATED errors? Because that means > they will break with 8 (which by your own words is closer to 2-3 years > out than 9-10). Absolutely no date is planned to switch E_DEPRECATED to = E_RECOVERABLE_ERROR. It must be clear for everyone that we don't have to = hurry there. My personal opinion is that it cannot be before at least 5 = years, and maybe more. If I had to announce a major version, I would say = 9, not 8. And no decision will be made before we have a large consensus = about it. Once again, there will be no good reason to hurry for it. Zeev, can't we put a sentence in the RFC where we state that the = E_DEPRECATED stage cannot be turned off before, say, 5 years at least ? = Once the statement is voted with the RFC, users are protected. Regards Fran=C3=A7ois