ID:               16064
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
 Status:           Open
 Bug Type:         Arrays related
 Operating System: RH 7.1
 PHP Version:      4.0CVS-2002-03-1
 New Comment:

Oops, forgot to include the link:

http://bugs.php.net/bug.php?id=17279


Previous Comments:
------------------------------------------------------------------------

[2002-05-16 16:24:37] [EMAIL PROTECTED]

Your second example isn't like the first.  $a[0] is a reference to
itself.  The first bonks because $GLOBALS['GLOBALS'] is a reference to
$GLOBALS.  An equivalent is:

<?php
$a=array(1,2,3);
$a[3]=&$a;
array_merge_recursive($a,$a);
var_dump($a);
?>

which will produce the same results.  I'm submitting a feature request
for array_recurse_safe($array) which returns an array with no infinite
loops.

------------------------------------------------------------------------

[2002-03-14 09:33:52] [EMAIL PROTECTED]

OK. status -> open

------------------------------------------------------------------------

[2002-03-14 09:31:58] [EMAIL PROTECTED]

streplace('them','him',$previous_vote);

------------------------------------------------------------------------

[2002-03-14 09:30:40] [EMAIL PROTECTED]

I have talked to Zeev about this issues. Asked them may I have to fill
bug report and he said:
"They should either use hash_apply(), which automatically protects
against 
recursion, or implement the recursion protection themselves (like
print_r() 
does).  You can/should open bug reports about them..."
In the start Zeev talks about some functions that have problems with
$GLOBALS and arrays that holds elements pointing ot itself.

------------------------------------------------------------------------

[2002-03-14 09:23:45] [EMAIL PROTECTED]

I'm sure you can come up with a load of nasty things you can do with
$GLOBALS, but what do you want us to do about it? Disable $GLOBALS for
use with array_* functions (it that's even possible)? Disable $GLOBALS
at all?

------------------------------------------------------------------------

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/16064

-- 
Edit this bug report at http://bugs.php.net/?id=16064&edit=1

Reply via email to