ID: 37746
User updated by: glideraerobatics at hotmail dot com
Reported By: glideraerobatics at hotmail dot com
Status: Wont fix
Bug Type: XMLRPC-EPI related
Operating System: FreeBSD 6.1
PHP Version: 5.1.4
New Comment:
Ok, but then the question:
Could a 'mixed' array be of any use in xmlrpc communication if the
numeric keys are being lost? I can't (yet) see how anybody could be
relying on that because the xmlrpc response is useless/invalid in such
cases.
Previous Comments:
------------------------------------------------------------------------
[2006-06-21 08:19:02] [EMAIL PROTECTED]
Well, 4 years with an unknown amount of people relying on it.
[EMAIL PROTECTED]:~$ cli -r 'var_dump(xmlrpc_get_type(array(123=>123)),
xmlrpc_get_type(array("a"=>123)),
xmlrpc_get_type(array(123=>123,"a"=>123)));'
string(5) "array"
string(6) "struct"
string(5) "mixed"
------------------------------------------------------------------------
[2006-06-21 01:36:19] glideraerobatics at hotmail dot com
I'm confused. Is "It's been that way since the very first release" the
reason why it won't be fixed?
I'm glad Microsoft didn't think that way otherwise I'ld still be seeing
multiple BSOD's every day.
------------------------------------------------------------------------
[2006-06-19 08:20:56] [EMAIL PROTECTED]
It's been that way since the very first release, if the array contains
numeric indices only.
------------------------------------------------------------------------
[2006-06-08 15:02:04] lars dot maes at gmail dot com
I confirm this bug on Debian 3.1a sarge with php4 version 4.3.10
The chr(0x00) solution also works
------------------------------------------------------------------------
[2006-06-08 14:16:45] glideraerobatics at hotmail dot com
By the way, a quick workaround to the problem is to append a NULL byte
to the keys:
$key1 = '666' . chr(0x00);
This way the hash is returned as a correct xml-rpc response without the
NULL bytes.
------------------------------------------------------------------------
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/37746
--
Edit this bug report at http://bugs.php.net/?id=37746&edit=1
