On 11/19/2010 06:16 AM, Dmitry Stogov wrote:
Derick Rethans wrote:
On Thu, 18 Nov 2010, Christopher Jones wrote:
On 11/18/2010 06:26 AM, Dmitry Stogov wrote:
The proposed patch allows compiling PHP with --enable-zend-multibyte
and then enable or disable multibyte support at run-time using
zend.multibyte=0/1 in php.ini. As result the single binary will be
able to support multibyte encodings and run without zend-multibyte
overhead dependent on configuration.
The patch doesn't affect PHP compiled without --enable-zend-multibyte.
I'm going to commit it into trunk before alpha.
Any objections?
If the overhead of zend.multibyte=0 is negligable, then why not remove
remove the configure option altogether? This would reduce the
complexity of the implementation and simplify building & maintenance.
Why have two interdependent ways to get the same outcome if one way
will do?
Because it has a dependency on mbstring.
Actually, it doesn't have compile-time dependencies, so it's probably make
sense to remove --enable-zend-multibyte completely.
Thanks. Dmitry.
Derick
Another ease-of-use simplification prior to releasing 5.3.4 is to roll
back the addition of ZEND_MULTIBYTE
http://svn.php.net/viewvc?view=revision&revision=305266
In future an ini_get() for zend.multibyte would be the solution for
http://bugs.php.net/bug.php?id=52348
Chris
--
Email: christopher.jo...@oracle.com
Tel: +1 650 506 8630
Blog: http://blogs.oracle.com/opal/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
