> -----Original Message-----
> From: Marco Pivetta <ocram...@gmail.com>
> Sent: Thursday, September 12, 2019 5:59 PM
> To: Zeev Suraski <z...@php.net>
> Cc: PHP Internals List <internals@lists.php.net>
> Subject: Re: [PHP-DEV] Changing fundamental language behaviors
>
> If you want to have an authoritative say on what the RFC process is for or
> not,
> please start a new RFC about it: your mail is just straight out inappropriate.
No Marco. The RFC process wasn't meant to deal with who has authoritative say
any more than it was meant to deal with changing fundamental behaviors in PHP.
The fact we got used to putting everything to a vote doesn't mean that it can
work for anything and everything.
While I realize my email is unpleasant for many to read, it's in the context of
an RFC that attempts to do something that is strictly inappropriate and out of
the question. Stating the fact, that the RFC process was never meant to allow
this to be done, is a statement of fact.
I *hate* to be in the position to be the one who has to point it out and stick
to it. I know how much fire that's going to draw and I know I'd hate every
second of it. But it is what it is.
There are no processes to make fundamental non-opt-in language changes in PHP.
There won't be such processes either. These behaviors are here to stay. We
can tweak them, we can augment them - we do not get to deprecate or radically
change them.
We can (and I believe should) augment them with alternative, stricter opt-in
behaviors. But those who dream of simply changing PHP into a stricter language
step by step should understand that this is simply not going to be happen. Not
now, not ever.
Zeev
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
