Re: mbstring and 4.3.0
| From: | Moriyoshi Koizumi | Date: | Fri, 08 Nov 2002 06:06:49 +0000 |
| Subject: | Re: mbstring and 4.3.0 | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-90632@lists.php.net to get a copy of this message | ||
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.
>
> -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.php
>