> Am 24.03.2015 um 14:39 schrieb François Laupretre <franc...@php.net>: > >> De : Nikita Popov [mailto:nikita....@gmail.com] >> >> The mbstring extension supports replacing PHP string functions with >> multibyte variants through the mbstring.func_overload ini option. >> >> This ini setting is a real PITA for code compatibility, as it makes it >> impossible to rely on the output of even the most basic PHP functions, like >> strlen(). Security-critical code in libraries and frameworks typically >> handles this issue by conditionally using either strlen() or 8bit >> mb_strlen(). Apart from that, the issue is generally ignored. >> >> If we do not wish to drop support for this option in PHP 7, I would at >> least suggest to deprecate it. > > Probably fine, but how does your suggestion fit in the PHP 7 timeline ? The > BC break requires it is introduced in 7.0. And it is too late for this. As > everyone seems to be against delaying the timeline, I hope we won't accept > exceptions. > > Regards > > François
No, he isn't asking for delaying the timeline. He's asking if we can do this without RFC. Minimal self-contained changes don't need a RFC and can go as well into alpha/beta phase without issues. Nikita, I assume with dropping you meant throwing a warning in case the option is detected and remove its functionality? Removing it completely in 7.0 may cause silent failures... If yes, I'm fine with dropping that ini switch. Thanks, Bob -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
