Question/comment about the Array to String conversion RFC
| From: | Zeev Suraski | Date: | Mon, 02 Mar 2015 14:24:09 +0000 |
| Subject: | Question/comment about the Array to String conversion RFC | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-84168@lists.php.net to get a copy of this message | ||
All,
https://wiki.php.net/rfc/array-to-string
(which I voted yes to) deviates
from our guidelines of deprecating features first, and removing them
later; It’s addressed in the RFC – but I’m a bit worried that this opens
the door to jumping from any sort of notice/warning into errors or removed
features without any deprecation phase.
In comparison, in Nikita’s RFC for removing E_STRICT – there aren’t any
proposed ‘jumps’ to E_RECOVERABLE_ERROR that don’t first go through
E_DEPRECATED.
Should we not go through this deprecation cycle, even if may feel anxious
to get rid of this behavior?
Zeev