Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108195 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 98739 invoked from network); 18 Jan 2020 23:24:08 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 18 Jan 2020 23:24:08 -0000 To: internals@lists.php.net References: Date: Sat, 18 Jan 2020 21:32:07 +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: [PHP-DEV] Re: [RFC] "use global functions/consts" statement From: marandall@php.net (Mark Randall) Message-ID: On 18/01/2020 18:05, tyson andre wrote: > which is now declare(disable_ambiguous_element_lookup=1) at the top of a file. I_suspect_these_long_declares_might_get_tedious Can we at least agree on internals that a declare doesn't have to have a negative default value that is toggled on? I'd much rather have something like: declare(ambiguous_element_lookup=0) declare(ambiguous_element_lookup=off) -- Mark Randall marandall@php.net