On 03/03/16 09:34, Tony Marston wrote: >> The "var" keyword once emitted an E_STRICT but I guess it was turned off >> again because too many people were complaining as they are now. > > So if people are still using it then surely that is an argument AGAINST > its removal.
The underlying problem here IS things like E_STRICT and E_DEPRECATED. On one hand YES you can get legacy code working by hiding the warnings, but that only makes the problem worse when someone actually completes the cycle and removes the keyword. Getting code through the PHP5.2/3/4 cycles did require leaving all messages visible and handling each as required. The problem with 'var' is that while one should probably replace them all with public, there is a lot of simple legacy code still in active use that could take years to 'tidy' and for no gain what so ever? A quick scan of my current code base shows several thousand hits on 'var ' in both third party libraries, stock code and private stuff. Only a small percentage are 'actually' replaceable by public but the time to go through and manually check each one ... is it THAT much of a problem? -- 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
