Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107051 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 32235 invoked from network); 13 Sep 2019 10:34:23 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 13 Sep 2019 10:34:23 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id F1FF52C143C for ; Fri, 13 Sep 2019 01:10:27 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.0.0.0/16 X-Spam-Virus: No Received: from mail.gna.ch (www.gna.ch [IPv6:2001:8a8:21:3::1:80]) by php-smtp3.php.net (Postfix) with ESMTP for ; Fri, 13 Sep 2019 01:10:27 -0700 (PDT) Received: from [10.0.1.55] (77-56-180-37.dclient.hispeed.ch [77.56.180.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by darkcity.gna.ch (Postfix) with ESMTPSA id 37BFB20E4B for ; Fri, 13 Sep 2019 10:10:25 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Fri, 13 Sep 2019 10:10:24 +0200 References: <076701d56978$86020910$92061b30$@php.net> <078e01d5697c$5512bc10$ff383430$@php.net> <31BD63BC-ACE0-4478-B241-E698D2D6F59C@newclarity.net> <77CA024D-3141-4707-8280-81CA78282AFA@newclarity.net> To: PHP internals In-Reply-To: Message-ID: X-Mailer: Apple Mail (2.3445.104.11) X-Envelope-From: Subject: Re: [PHP-DEV] Changing fundamental language behaviors From: cschneid@cschneid.com (Christian Schneider) Am 13.09.2019 um 09:41 schrieb Lester Caine : > On 12/09/2019 23:16, Mike Schinkel wrote: >> Those who vote on this list will decide if breaking WordPress = end-user's site bothers them or not. That's something too few people on this list seem to be aware of: Breaking other people's perfectly functional code because you believe in = a different coding style is not something which should be done easily. > So we *DO* need an LTS version of PHP that will run perfectly = functional websites for the next ten years while others create the next = replacement for the likes of WordPress by moving framework functionality = inside PHP ... I agree! Which means there will be additional burden on the PHP core developers = as there will be another version to back port security fixes to for a = long time. Also not a decision to be made lightly. While I do like democracy I also agree with Zeev that it is too easy for = people to vote yes on a breaking change even if they didn't think it = through. So if you voted yes for any change of a notice/warning to an exception = (which will break things) please reconsider! Is it really worth it? And if you really think so, could we make it = opt-in? Or at least globally opt-out-able? - Chris