On 16/03/15 03:29, Yasuo Ohgaki wrote: > > I agree partly. It does not provide any additional feature. > However, it gives users ability to detect bugs. It's important gain for > users also. > > Wrong code should be fixed anyway. The RFC could be more old code friendly > if E_DEPECATED is used.
The problem here is simply that just what error's are enabled and disabled is getting more difficult to decide? If when moving from a currently clean environment which has every error displayed and only shows something when any problem arises then moving to a new major version do we have to switch everything off again since all types of errors will now be thrown by the previously clean code. This is the problem currently in the PHP5.2->5.4 dilema. Yes you can switch errors off and the code runs, but then how do you address the problems. Added to which something hidden by E_DEPECATED in 5.3 is now no longer available in 5.4, but the code is still 5.2. Adding the errors is not really the problem it's working out the order they need to be cleared in :( -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
