mirror of
https://github.com/php/php-src.git
synced 2024-09-28 21:36:12 +00:00
41e9ba6333
Previously mb_chr() had two different encoding-dependent behaviors: * For "Unicode-encodings" it took a Unicode codepoint and returned its encoded representation. * Otherwise it returned a big-endian binary encoding of the passed integer. Now the input is always interpreted as a Unicode codepoint. If a big-endian binary encoding is what you want, you don't need mbstring to implement that. |
||
---|---|---|
.. | ||
libmbfl | ||
oniguruma | ||
tests | ||
ucgendat | ||
.gitignore | ||
config.m4 | ||
config.w32 | ||
CREDITS | ||
mb_gpc.c | ||
mb_gpc.h | ||
mbstring.c | ||
mbstring.h | ||
oniguruma.patch | ||
php_mbregex.c | ||
php_mbregex.h | ||
php_onig_compat.h | ||
php_unicode.c | ||
php_unicode.h | ||
README | ||
README_PHP3-i18n-ja | ||
README.libmbfl | ||
unicode_data.h |
!!Caution: DO NOT ADD/CHANGE MBSTRING CODE!! New mbstring is under development, anyone who would like add new feature/change behavior should access to development source. http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/php-i18n/ All changes made after 2002/5/19 are subject to be removed. You are warned in php-dev and php-cvs lists many times already. If you are curious, search archive for details. Thank you.