[PHP-DEV] Reference handling change and PHP 4.4.0

2005-09-13 Thread Colin Tucker
Hello all, I know this issue has most likely been discussed to death here so I apologise in advance for starting a new thread about it. I just need to get my head around the reasoning for introducing this change to PHP4 (4.4 branch). I can understand making the change to PHP5, but can someo

Re: [PHP-DEV] Reference handling change and PHP 4.4.0

2005-09-13 Thread Colin Tucker
Hi Jani, Yes, the increase in the middle digit. ;) Ok, so does this mean that the 4.3.x and 4.4.x branches will now be updated separately? Say, if a serious vulnerability was detected in 4.3.x an 4.4.x, and separate release would be issued for both? Kind regards, Colin. Jani Taskinen wro

Re: [PHP-DEV] Reference handling change and PHP 4.4.0

2005-09-13 Thread Colin Tucker
Hi Rasmus, thanks for replying, I appreciate your feedback. Rasmus Lerdorf wrote: We have been looking to see if there is a way to fix the memory corruption issue in a way that has less of an impact on existing code. This doesn't change the fact that every error you get is actually an error in t

Re: [PHP-DEV] Reference handling change and PHP 4.4.0

2005-09-13 Thread Colin Tucker
Rasmus Lerdorf wrote: Once again, it is an E_NOTICE in 4.4. And yes, not displaying it makes it go away. Staying with 4.3 because of this is nuts. If you are seeing this notice under 4.4 that means you are most likely getting random memory corruption under 4.3. Move to 4.4 to fix the memory c

Re: [PHP-DEV] Reference handling change and PHP 4.4.0

2005-09-14 Thread Colin Tucker
Derick Rethans wrote: We found this out the hard way yesterday when our server administrator upgraded our production server to PHP 4.4.0 (even though the Debian package description said it was a PHP 4.3.x release). We ended up with hundreds of errors and many, many vhosts stopped working correct

Re: [PHP-DEV] Reference handling change and PHP 4.4.0

2005-09-14 Thread Colin Tucker
Derick Rethans wrote: But it just could as well have been because he was relying on the memory corruptions. Hard to tell without code. Derick As 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 woul

Re: [PHP-DEV] Reference handling change and PHP 4.4.0

2005-09-14 Thread Colin Tucker
Rasmus Lerdorf wrote: So while the tone of some of these messages may not be great, > often the suggestion that the code in question isn't very good is accurate. Rasmus, I think where some of the concern and confusion lies is with those of us who have been doing, or at least attempting, some

[PHP-DEV] Re: Reference handling change and PHP 4.4.0

2005-09-15 Thread Colin Tucker
Hello again, Wow, this thread generated more heat than I thought it would, I basically just wanted to know the reasoning behind making the change to PHP4, unfortunate I guess for all involved that it went downhill. I have learned much in the past few days, at any rate. As mentioned, my code