Bug #48697 [Com]: mb_internal_encoding() value gets reset by parse_str()

Edit report at http://bugs.php.net/bug.php?id=48697&edit=1 ID: 48697 Comment by: jan dot hancic at gmail dot com Reported by: glen at delfi dot ee Summary: mb_internal_encoding() value gets reset by parse_str() Status: Closed Type: Bug Package: mbstring related Operating System: PLD Linux PHP Version: 5.2.10 Assigned To: moriyoshi New Comment: This bug is still present in version 5.2.10 (FreeBSD XXXX 7.2-RELEASE FreeBSD 7.2- RELEASE #0: Fri May 1 07:18:07 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64). Previous Comments: ------------------------------------------------------------------------ [2009-09-14 05:20:41] glen at delfi dot ee nevermind, disregard my last post, seems commit is posted to bug, just not mailed to bug subscribers... ------------------------------------------------------------------------ [2009-09-14 05:18:41] glen at delfi dot ee blah, why you never include scm commit in the bug? would be helpful instead have to dig myself.... ------------------------------------------------------------------------ [2009-09-14 04:12:54] moriyoshi@php.net Changed the summary again as it turned out mb_parse_str() has nothing to do with this. ------------------------------------------------------------------------ [2009-09-14 04:11:48] moriyoshi@php.net This bug has been fixed in SVN. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ [2009-09-14 04:11:29] svn@php.net Automatic comment from SVN on behalf of moriyoshi Revision: http://svn.php.net/viewvc/?view=revision&revision=288301 Log: - Looks like bug #48697 has already been fixed in RC1. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/bug.php?id=48697 -- Edit this bug report at http://bugs.php.net/bug.php?id=48697&edit=1