On 04/11/14 14:45, Peter Lind wrote: > I'd suggest an alternative: fork PHP and only merge bugfixes in to your > own version. Best of both worlds, you get to keep your beloved PHP > pristine without any of the cumbersome new features, and the rest of us > can enjoy an evolving language.
In hind sight that is perhaps a choice that SHOULD have been made when e_strict was introduced. I still have a lot of code that will not run on a stock PHP5.4 installation but is running live sites quite happily on an older setup and care has to be taken of any security problems found anyway. The evolution I am still awaiting is to be able to use the unicode material I have in the databases directly in PHP arrays rather than having to take care of ordering externally ... and that perhaps is the only reason I didn't freeze ... -- 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
