Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101874 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24862 invoked from network); 15 Feb 2018 07:17:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Feb 2018 07:17:48 -0000 Authentication-Results: pb1.pair.com header.from=php@fleshgrinder.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=php@fleshgrinder.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 212.232.28.122 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 212.232.28.122 mx201.easyname.com Received: from [212.232.28.122] ([212.232.28.122:57259] helo=mx201.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/67-26725-914358A5 for ; Thu, 15 Feb 2018 02:17:47 -0500 Received: from cable-81-173-134-149.netcologne.de ([81.173.134.149] helo=[192.168.178.20]) by mx.easyname.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1emDnS-0004pr-CK; Thu, 15 Feb 2018 07:17:36 +0000 Reply-To: internals@lists.php.net To: Mcmuffin Mcguffin , internals@lists.php.net References: Message-ID: <590450c7-cb49-0e8c-c974-e44cf47f854b@fleshgrinder.com> Date: Thu, 15 Feb 2018 08:17:34 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-DNSBL-BARRACUDACENTRAL: YES X-DNSBL-PBLSPAMHAUS: YES Subject: Re: [PHP-DEV] Suggested change: change priority of new and -> From: php@fleshgrinder.com (Fleshgrinder) On 2/8/2018 7:38 PM, Mcmuffin Mcguffin wrote: > What do you think? > > Jaroslav Wegner > Thanks for the hard work to figure out what the roots of this annoyance is. This could land in the next PHP version, considering that many other breaking changes were also allowed in the past, given the following prerequisites: * RFC with a 2/3 majority vote * Tool to convert any possibly broken code into valid code (basically putting parenthesis around any complex `new (...)()`). * Update to https://github.com/php/php-langspec/blob/master/spec/10-expressions.md#the-new-operator -- Richard "Fleshgrinder" Fussenegger