Re: [RFC] [DISCUSSION] Deprecate PHP's short open tags V2
| From: | Mark Randall | Date: | Wed, 24 Jul 2019 00:37:42 +0000 |
| Subject: | Re: [RFC] [DISCUSSION] Deprecate PHP's short open tags V2 | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-106273@lists.php.net to get a copy of this message | ||
On 23/07/2019 21:58, Stanislav Malyshev wrote:
I think nicer would be to explain why we need second RFC and what it adds to the previous one. If I didn't get some context, please explain.The previous one, as written, carried a high probability of silently leaking both code and data, but these arguments against it only gained prominence after the RFC had already passed. V2 remedies that by maintaining default INI behaviour, as well as nullifying the possibility of code / data leaks by throwing a compiler exception if <? is encountered (and enabled), thus denying the VM an opportunity to execute a file which contains potentially leaky code. If short tags are to be removed, V2 is a significantly more reasonable way of going about it. -- Mark Randall