Re: Reference handling change and PHP 4.4.0
| From: | Colin Tucker | Date: | Wed, 14 Sep 2005 22:37:22 +0000 |
| Subject: | Re: Reference handling change and PHP 4.4.0 | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18939@lists.php.net to get a copy of this message | ||
Derick Rethans wrote:
But it just could as well have been because he was relying on the memory corruptions. Hard to tell without code. DerickAs I mentioned in my reply to Rasmus above, the problem seems to be stemming from a class that acts like a map of objects. Most of my PHP4 code would pass objects around by reference to ensure operations were working on the original object, thus avoiding the creation of copies. After the upgrade to 4.4.0, the map lost integrity in that returning any object within the map by key would return the object last added to the map. I may not have provided any code, but this problem description was enough for Todd Ruth to send me a very helpful and informative e-mail on the matter (i.e. "everything the same as the last added" bugs), which shall help me greatly in tracking it down (thanks again, Todd!). Regards, Colin.