changes in ext/mbstring (PHP_4_3)

Rui,

4_4 branch is fine, however there is a very good chance there will not be a
PHP 4.4 release. At least at the present time there is no clear concensus on
the matter. Some think it would be a good idea to have a transitional release
between 4.3 & 5.0 and others believe making 4.4 would detract valuable
developer time, better spent releasing 5.0. This said you are more then
welcome to commit your changes to PHP_4_4 branch, but please be aware that it
may not end up being in any release. If the time & effort to make this
possible is significant, I'd recommend waiting till the status of release(s)
past 4.3.X is finalized.

Ilia

Ilia,

I understand your opinion. The stable release has priority in PHP_4_3
branch.
I will skip to commit for PHP_4_3 branch, and I commit this change for
upcoming PHP_4_4 (4.5?) branch.

Rui

On Sun, 21 Sep 2003 12:26:25 -0400

Ilia Alshanetsky ilia@prohost.org wrote:

PHP_4_3 is strictly for bug fixes, no major changes code and
functionality changes should occur to prevent introduction of new bugs
into a stable code base. As such, as a 4.3.X Release Master I am strongly
opposed to this change.

Ilia

ext/mbstring/mbfilter* and some related files were developed as
the general library to convert multi-byte character encoding and these
files were bundled with PHP since PHP 4.0.6.

The original library is developed as libmbfl in sourceforge.jp.
(You can obtain libmbfl from
http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/php-i18n/libmbfl)

The bundled files (mbfilter*) with PHP are replaced the bundled version
of libmbfl in CVS head branch (PHP5-dev).

These changes are to minimize the difference of the original library
and the bundled version with PHP and to minimize the developing effort.

I have plan to commit the same changes to PHP_4_3 branch.
If someone has problem with these changes, please let me know.

Rui

--
Rui Hirokawa rui_hirokawa@ybb.ne.jp

--
Rui Hirokawa <rui_hirokawa@ybb.ne.jp