Just got back from Sri Lanka and am catching up on email. But in general I don't agree with your statement that things that are quiet in 5.0.4 must be quiet in 5.0.5. Quietly corrupting memory doesn't really work. Sometimes we need to break things slightly to fix things. My message was more about if there was a better way to fix it. I looked at the code and couldn't tell if it was somehow possible to catch this on the write instead of on the call. It sounds like that isn't possible. The second approach to try to regain some backwards compatibility is to make some of our internal functions aware of the fact that they are being passed a ref to a temp var and if so pretend it wasn't passed by reference.
-Rasmus Pierre Joye wrote: > Hi Rasmus, > > You start a new thread for my question, maybe you will get more > answers or at least better ones. > > If it is a reference or not, I do not care, it should not "act" > differently. Understand that a quiet code in 5.0.4 must be quiet in > 5.0.5. > > If we add notices in 5.1.0 and then make them fatal in 5.2.0, I'm > fine. People will have time to migrate and "fix" their code. > > Regards, > > --Pierre > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
