On 10/08/16 12:14, Michał Brzuchalski wrote: > @Peter and @Rowan: Very good point and sounds reasonable, I also thing > there is need for evolution. Idea of fork PHP and never update made me > laugh to tears :)
To be quite honest ... I do now wish that I had simply forked PHP5.3 and maintained that with security fixes, although the ISP's who still support that have done a reasonable job. I decided that it was better to pull everybody over to PHP5.4 and so all the older services could be shut down, but it is not a 5 minute job transferring a legacy site and there are still a large number left to resolve. More irritating is that I have a framework that I've moved everything onto so as to loose the the legacy problems altogether, but while it runs perfectly cleanly on PHP7, it is not written in a style that allows things like 'namespace' to be integrated. Some of the libraries ARE being reworked in a manor that 'modernises' them, but most definitely breaks compatibility with existing code. Things like moving from Smarty 2 to Smarty 3 and then loosing the compatibility wrapper took months, but now the new 'loader' for Smarty 3 is clashing with the legacy Smarty based projects and it is that sort of hassle that simply crushes any pleasure in coding these days, when there is nothing gained by this move to 'auto-loading' libraries as the standard for everybody. -- 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
