ID: 29687 User updated by: jakub dot phpbug at horky dot net Reported By: jakub dot phpbug at horky dot net -Status: No Feedback +Status: Closed Bug Type: Scripting Engine problem Operating System: * PHP Version: 6CVS-2006-04-28 (snap) New Comment:
Yes, the problem appears to be solved in the new version. Thanks. Previous Comments: ------------------------------------------------------------------------ [2007-08-04 01:00:00] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2007-07-27 05:13:50] j...@php.net Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows (zip): http://snaps.php.net/win32/php5.2-win32-latest.zip For Windows (installer): http://snaps.php.net/win32/php5.2-win32-installer-latest.msi ------------------------------------------------------------------------ [2006-04-28 19:21:51] jakub dot phpbug at horky dot net (Also note that unlike bug #28939, there are _referenced_ arrays in question.) ------------------------------------------------------------------------ [2006-04-28 19:10:44] jakub dot phpbug at horky dot net Please review the bug. It ISN'T bogus indeed, although it appears so. The code snippet provided proves that the behavior is really incorrect. Admit that when you only "touch" the array (by read-only function such as key()), you lose your reference-passing? More, you don't lose it in current cycle but in the NEXT cycle and subsequent? Hmm... I tested it on today's snap and still the same behavior. I'm really looking forward to the moment when I can remove the workaround from all reference-passed foreachs from all of my projects... thanks. ------------------------------------------------------------------------ [2005-06-19 02:00:07] sni...@php.net See bug #28939 ------------------------------------------------------------------------ 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/29687 -- Edit this bug report at http://bugs.php.net/?id=29687&edit=1
