Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82042 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46684 invoked from network); 6 Feb 2015 14:18:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Feb 2015 14:18:05 -0000 Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:50545] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4F/42-45146-B1DC4D45 for ; Fri, 06 Feb 2015 09:18:05 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id DB88B4B008C; Fri, 6 Feb 2015 15:14:38 +0100 (CET) Reply-To: To: "'Yasuo Ohgaki'" , "Dmitry Stogov" , "Pierre Joye" Cc: "'Ivan Enderlin @ Hoa'" , References: <54D37D41.2030706@hoa-project.net> <54D470FA.6000303@hoa-project.net> <02d301d041f3$0c5f3990$251dacb0$@tekwire.net> In-Reply-To: Date: Fri, 6 Feb 2015 15:17:53 +0100 Message-ID: <031501d04217$b393bff0$1abb3fd0$@tekwire.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: AQGgxP9HPTh52uHWkGo6jLSeXRdtNAG/QBJNAaMNlcwCFsMP6wB6oLwcArkn1nkCRuYlGQKZuynVnNYzS4A= Content-Language: fr X-Antivirus: avast! (VPS 150205-1, 05/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Design by Contract From: francois@tekwire.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : yohgaki@gmail.com [mailto:yohgaki@gmail.com] De la part de Yasuo = Ohgaki > Personally, backward compatibility is not too important.=20 > PHP5 is dead by PHP 7.2 release... This is the reason why. > It's only 3 years later, only 2 years later after PHP 7.0 release. That's where we disagree, as I think it's most important. Thinking that PHP 5 is dead in 3 years is extremely na=C3=AFve IMO. You = probably didn't live the PHP 4/5 migration but I guess we won't have = more than 30 % of production servers under PHP 7 in 2018, just due to = the delays of distros, hosting companies, and others. Now, suppose you're distributing a library or a framework, like Symfony, = Doctrine, etc. Someone tells you : "Here's the new DbC feature. You can = use it but this implies splitting your code to two independent branches = and maintain them in parallel until you have no PHP 5 customer = anymore.". What do you think you'll do (or won't do) ? @Pierre,@Dmitry : you have a better vision than mine on the migration = process. What's your opinion on forcing software developers to maintain = two separate branches ? Once again, the conditions in @assert lines ARE PHP code. There's no new = syntax. There is no real difference between writing = 'assert()' and '@assert ', especially if the = require/ensure blocks should contain 'assert' statements only. > What I believe is not important to you. I could be wrong. It is important. As I may be wrong too. Cheers Fran=C3=A7ois