Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107037 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 26936 invoked from network); 13 Sep 2019 02:20:36 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 13 Sep 2019 02:20:36 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id C1CCA2C0E46 for ; Thu, 12 Sep 2019 16:56:36 -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=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MIME_QP_LONG_LINE, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: X-Spam-Virus: No Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Thu, 12 Sep 2019 16:56:36 -0700 (PDT) Received: by mail-wr1-x430.google.com with SMTP id q17so25515155wrx.10 for ; Thu, 12 Sep 2019 16:56:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NQkExb72EJ3/1txv2lNG8X8mrdnqE9y15olRmLcwfPc=; b=bBqijFikdha/NABaiGhp1yhFo/zFnvU0DF0Ef/93KDKCf3lYu9czebNPKMReNWA+SD Va2YKlQqgRY/EfKNQvCmIVO2gYgvs70I0Vf8fyEcYEL9cHy0vSAR3OX1D7Ue1FOPnxDs tbE9s6laYA7VsOySyDh5qcutv88V8G8NdE7MgLeEOIWOxizOe3+Xyb20VHYGoflffuJf cWnu0xMQD3E0cOyhucs4BqW4XIyEAv6WPM1d6JrKFgvS43+T1REt1skbnwg+ElDSSRHh /VZXpLTgpdu9DNbyp2k+xezxb5YMZtG/ldffxRWzcIQGHscEcZzgaYK9g5WsdOU7HqTs nd4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NQkExb72EJ3/1txv2lNG8X8mrdnqE9y15olRmLcwfPc=; b=ryrgepMhTGHDM9LBJpbeVAiLj+3Er7FaIigl8FCsFx/jmBAJcnYW6Tck1QkXNfcZCb fXQTh81KbqerZXPtRr4gRph6il9smqTXpT98cUfS2D/NnVqTymvZqk2rqGZeK5/9Z8cJ l28p6xIxJp3wdQOFbeF1jr45U1j75BWvrWv3JmOG2b/Dk/qlj8Dls0FYWtuvncTstafq 59PtPaEHVMBIH8XCrbMtOzRuim3HJrSPsy76FL5EVYo64JhY7wBRsj2W5omtG6nfbV15 NZkMHR+Bnl9lk4mDvbooyANXy2urtb9wb6c23GAV7sMjSvOYlpjxC43uykn7sv1K0FBw metQ== X-Gm-Message-State: APjAAAWKZzXrZkCWywjQKKCB65zNR1DX7qjCcjfU0Odv/+3kc7UQv9jy qmqHo54Eg8vJyq0xNDUGeN8= X-Google-Smtp-Source: APXvYqyUJ0V/bUFsmU8dSlRio8yX0EX7wZmcaCQANJjGx1lvcM0kzXm8A1S75nDHkWc5SrL78vU0HA== X-Received: by 2002:a5d:4ac5:: with SMTP id y5mr31752576wrs.179.1568332594554; Thu, 12 Sep 2019 16:56:34 -0700 (PDT) Received: from [192.168.0.112] ([77.137.81.220]) by smtp.gmail.com with ESMTPSA id f17sm20930078wru.29.2019.09.12.16.56.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Sep 2019 16:56:33 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-AEE4C6B8-4102-47A5-A225-B6974BC49636 Mime-Version: 1.0 (1.0) X-Mailer: iPhone Mail (16G102) In-Reply-To: Date: Fri, 13 Sep 2019 02:56:30 +0300 Cc: PHP Internals List Content-Transfer-Encoding: 7bit Message-ID: 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> <52703F2F-BBB5-410C-800E-B759797F531C@zend.com> To: Joe Watkins X-Envelope-From: Subject: Re: [PHP-DEV] Changing fundamental language behaviors From: vsuraski@gmail.com (Zeev Suraski) --Apple-Mail-AEE4C6B8-4102-47A5-A225-B6974BC49636 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable > On 13 Sep 2019, at 2:50, Joe Watkins wrote: >=20 > Zeev, >=20 > > Without getting to the technicalities, simply put, no. >=20 > I'm not sure what you intend to do to stop it. I sincerely hope reason will prevail and we won't have to find out (as I was= hoping this part of the RFC won't be put up for a vote so that we wouldn't b= e in this mess to begin with). I am not looking forward to it - but we will= not be depreciating fundamental language functionality regardless of the re= sults of this or any other RFC - as RFCs have no mandate to do that. That i= s a statement of fact. Cheers, Zeev --Apple-Mail-AEE4C6B8-4102-47A5-A225-B6974BC49636--