Andrei Zmievski wrote:
At the PHP Conference in Germany several of us have discussed the
current state of mbstring and there was a proposal to not have it
enabled by default for 4.3.0 release. It seems that the extension
attempts to do magic stuff by overloading functions in the executor
globals and, as Thies said, that could be dangerous. Also, doesn't it
affect run-tests.php script currently?
AFAIK, it doesn't.
Comments are welcome.
Encoding translation, which is hard coded in 4.2.x or less, is
integrated and changeable by php.ini or .htaccess setting. And it's
default to off.
Function overloading is changeable by php.ini or .htaccess. It gives
flexibility porting single byte application to multibyte aware with a
lot less hassle. It's default to off and only changeable by INI_SYSTEM
and INI_PERDIR.
PHP 4.3.0's Zend Engine also comes with SJIS awareness. It does not
make sense to have SJIS awareness without mbstring also.
(Need compile option to enable SJIS awareness)
There are few modules that depend on mbstring. Current module loader
is not smart enough to detect dependency, too.
Unfortunately, PHP 4.2.3 has problem for handling array inputs, but
it's not mbstring developers' fault.
--
Yasuo Ohgaki
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
