Re: mbstring and 4.3.0
| From: | Dan Kalowsky | Date: | Fri, 08 Nov 2002 06:26:59 +0000 |
| Subject: | Re: mbstring and 4.3.0 | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-90633@lists.php.net to get a copy of this message | ||
It's interesting to me that this topic is brought up again and again about once every 3 or 4 months. The same points are rehashed each time, and the same result is reached, nothing is changed about mbstring. I believe this is partially because developers ask questions about mbstring, and receive no definitive answer to them (see the archives for a few examples).
Historically, I have been against mbstring being enabled by default. My feelings towards anything being enabled by default, unless it is considered core functionality, is pretty negative though.
On the flip side though, what exactly were these concerns brought up at the PHP Conference? Is it possible to share them with those of us who were not able to attend? Please include as much detail as possible.
On Friday, November 8, 2002, at 01:06 AM, Moriyoshi Koizumi wrote:
Hi, Now the transparent encoding conversion is disabled by default, and so is the function overloading. And the extension is not likely to cause any harm to other tests; recently some test failures related to output handlers were reported in fact, but the problem have been properly avoided. Then why do we even have to continue the same discussion? Is it the big deal how many people use mbstring? Now mbstring is not just for CJK people, because it also offers numerous unicode functionality. mb_convert_case(), contributed by Wez, is one of the examples. Besides I wonder why such dangerousness has not been warned up to now if that's the case. Moriyoshi Andrei Zmievski <andrei@gravitonic.com> 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? Comments are welcome.-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php ---------------------------------------------------------------<-Andrei http://www.gravitonic.com/* We are not a clone. * -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.phpDan Kalowsky "The future is always uncertain,
http://www.deadmime.org/~dank and the end is always near." dank-nom@aps-deadmime.org - "Roadhouse Blues", kalowsky@php.net The Doors