On 21/03/15 04:01, Nathan wesley wrote: > The old API should be deprecated in PHP 8.0 and removed completely in PHP > 9.0 (finally)
WHY? You don't HAVE to use the current API and wiping out all of the legacy code does not seem like a 'gain'. The two can co exist. > I hope that you take this seriously and tell me if there are any > limitations that prevents this from happening. I am currently working through a review of options to add one of those pop-up chat functions to my framework. There are several designs available, the majority of which as usual are charged for services, but once one culls those from the search results one gets back to a few where the code is ACTUALLY available open source. The problem however is that many of these libraries are now being written to 'modern standards' and this results in their being LESS reusable since the coding style makes them incompatible even with one another. I have managed to find ONE option which looks like it may be portable enough to convert to an installable package to work with the rest of my framework. Just have to convert every file from a single line of code back to something with a real layout so I can use it. A 120000 character long line works with PHP, but is just as unreadable as some of the new coding styles! YES some old code needs culling ... but equally there is just as much bad new code. Both have their place. Mind you in 10 years time I'll probably be dead and some one else will have to re-write the entire code base :) -- 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
