On 16/06/16 07:44, Dmitry Stogov wrote: > RFC also proposes a way to "fix" affected applications, wrapping constant > definitions, that may be redefined, with try/catch.
Doesn't anybody remember the problems which STILL have to be resolved with changes in PHP5.2/3/4 which require the assistance of programmers to fix naive users problems. Now many of the new features being added will not be currently used in legacy code, but can anybody ensure that all of the BC changes being currently pushed for will not cause a more general PHP5.4 style block to upgrading? HAVING to add changes to code to retain a legacy style of operation is something that should only happen in a major version. Isn't this why most big projects no longer bother with many small version changes? What is Firefox up to now ... However going down that root does require LTS builds which is something else which is maintaining PHP5.3 in the field. I am now getting used to the changes in PHP7, but the current roadmap for PHP7.1 is just another PHP5.4 in my book and it does create a case for my simply rolling back to PHP5 since none of my production systems have been fully updated so they can use PHP7 yet ... -- 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
