Re: Re: [RFC] "use global functions/consts" statement
| From: | tyson andre | Date: | Sat, 18 Jan 2020 18:05:35 +0000 |
| Subject: | Re: Re: [RFC] "use global functions/consts" statement | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-108193@lists.php.net to get a copy of this message | ||
Hi internals,
After feedback, the RFC syntax has been changed from
use global functions to
declare(disable_ambiguous_element_lookup=1). In addition,
- The two settings have been combined into a single option,
which is now declare(disable_ambiguous_element_lookup=1) at the top of a file.
Those settings would be enabled together, in any use case I can think of.
- Declaring global functions and constants in files with declare(disable_ambiguous_element_lookup=1)
is now allowed in any namespace,
to allow code to continue to work even with future changes such as https://wiki.php.net/rfc/namespace_scoped_declares
(and so that files declaring functions or constants can have consistent coding style with files
that don't)
- The following voting choices have been removed: (1) the syntax and for (2) whether declaring
functions/constants are errors
The outcome of those votes would noticeably change the RFC and affect whether voters would vote
for the RFC as a whole.
The RFC https://wiki.php.net/rfc/use_global_elements
has been updated.
The implementation at https://github.com/php/php-src/pull/4951 has
also been updated.
I was planning to move this to the voting stage on the 25th (1 week),
since the revised RFC is similar to the old RFC,
and arguments in favor of declare() have been mentioned for over 2 weeks.
Thanks,
- Tyson