Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108314 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 86479 invoked from network); 29 Jan 2020 11:55:42 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 29 Jan 2020 11:55:42 -0000 To: internals@lists.php.net References: Date: Wed, 29 Jan 2020 10:06:18 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 94.8.17.105 Subject: Re: [VOTE] declare(function_and_const_lookup='global') From: marandall@php.net (Mark Randall) Message-ID: > On Tue, Jan 28, 2020 at 8:22 PM tyson andre wrote: >> I've opened the vote on https://wiki.php.net/rfc/use_global_elements I too would like to thank you for the effort put in, but I find myself in agreement with several of the other posters that I'm not sure this is the right way to go about it. I'm not a fan of the disparity between classes and functions that this would introduce if used. Support for namespaced level functions is already quite poor (with lack of autoloading) and rather than try to gain a few bytes here and there, I think the better long-term option would be to simply remove support for them entirely in favour of static methods, and at that point the door is open to make functions and constants be global-only. -- Mark Randall