On 08/02/15 11:43, Ralf Lang wrote: > A lot of sites sticked with PHP5.3 because they were driven by > enterprise platforms which by definition won't upgrade during the life > cycle. That had its own costs and aches which are entirely not PHP's fault. > >> > PHP7 is proposing a LOT of shiny new features which will break much >> > legacy code. > Which features hurt you? Which features break code which would have been > best practice by php 5.0.0?
Currently it is impossible to run the PHP5.2 code base on PHP5.4. That is a simple fact. So I can't do between 5.2 and 5.4 what I am currently doing between 5.4 and 7. The code has to be reworked ... so what ever anybody says PHP5 .4 *IS* PHP6 in terms of major breaks. 'Best Practice' is at best dependent on just what style of working a particular faction wants. Is 'strict typing' an example of future best practice? Is e_strict compliant code best practice? It is that which I base the move from 5.2 to 5.4 on. If I add a library using namespaces often things fail to work so I stick with the 'non-namespace' version? Best practice these days is I suppose to be using composer for everything? None of this was around by 5.0.0 days yet the bulk of my framework code is well over 10 years old and at one time one could select you preferred database install and run. Nowadays just keeping a small subset of database engines working is all we can manage. PHP is no longer the simple user friendly base that it once was! -- 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
