Re: [RFC] [DISCUSSION] Deprecate PHP's short open tags V2
| From: | Stanislav Malyshev | Date: | Tue, 23 Jul 2019 20:22:01 +0000 |
| Subject: | Re: [RFC] [DISCUSSION] Deprecate PHP's short open tags V2 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-106258@lists.php.net to get a copy of this message | ||
Hi!
> Due to the controversy after the initial vote on the Deprecate PHP's Short
> Open Tag RFC [1] here is a new RFC to deprecate them written with the help
> of Nikita Popov <nikic@php.net>.
Could you please explain what has changed since the last time we
discussed it that makes it necessary to bring the second RFC on the same
topic? Did any arguments about the dangers of removing the short tags
somehow became invalid? If yes, then how? What necessitates changing the
results of that RFC almost immediately after it was implemented?
In the RFC, I read:
Worse than that, code using short open tags deployed on a server using
short_open_tag=0 will leak application code, because short open tags are
silently ignored.
I am not sure how it is supposed to be an argument for making such
behavior the default. Could you explain?
--
Stas Malyshev
smalyshev@gmail.com