Re: [RFC][DISCUSSION] Deprecate the backtick operator
| From: | Midori Koçak | Date: | Mon, 12 Feb 2018 09:16:16 +0000 |
| Subject: | Re: [RFC][DISCUSSION] Deprecate the backtick operator | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-101836@lists.php.net to get a copy of this message | ||
Sounded reasonable to me. At least for security.
On 11 February 2018 at 21:24, Stanislav Malyshev <smalyshev@gmail.com>
wrote:
> Hi!
>
> > It's absolutely impossible to treat notices as errors in PHP, so I
> > assume everybody thinks the same. If someone converts notices to
> > ErrorExceptions or something, it's their fault.
> > A notice in tests is exactly what a deprecation is supposed to do, force
> > people to update their code.
>
> If you force people to do something, by definition it is not "Backwards
> Incompatible Changes: None". If it were none, people would not be forced
> to do anything.
>
> > Regarding the notice level, it's a bit confusing picking one.
> > E_DEPRECATED, E_STRICT, E_NOTICE... I'm not sure what it should be.
>
> You should write all the details in the RFC. If you are not sure what to
> choose, write "I am not sure which one to choose here, options are X, Y
> and Z".
> --
> Stas Malyshev
> smalyshev@gmail.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>