Re: Deprecate or remove mbstring function overloads in PHP 7
| From: | Masaki Kagaya | Date: | Wed, 25 Mar 2015 02:47:15 +0000 |
| Subject: | Re: Deprecate or remove mbstring function overloads in PHP 7 | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-85457@lists.php.net to get a copy of this message | ||
Rui agreed the deprecation and Yasuo gave notice to PHP internal in April
2012.
https://bugs.php.net/bug.php?id=65785
http://marc.info/?l=php-internals&m=133548185505478&w=2
2015-03-25 0:25 GMT+09:00 Zeev Suraski <zeev@zend.com>:
> > -----Original Message-----
> > From: Nikita Popov [mailto:nikita.ppv@gmail.com]
> > Sent: Tuesday, March 24, 2015 4:45 AM
> > To: PHP internals
> > Subject: [PHP-DEV] Deprecate or remove mbstring function overloads in PHP
> > 7
> >
> > Hi internals!
> >
> > 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.
> >
> > Thoughts?
>
> I think we need to understand how it's actually being used before
> discussing
> its deprecation. IIRC it's extremely widely used in Japan, but could be
> wrong.
> I'd want to hear from our Japanese contributors what their thoughts are.
>
> Zeev
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>