On 07/11/14 01:59, Christoph Becker wrote: > Nobody suggested to switch off error reporting. IMO, E_STRICT is > supposed to be a weak form of E_DEPRECATED, i.e. a hint for the > developer to modernize the code in the near future. Until this can be > done, it seems to be perfectly fine to suppress *these* warnings. When > the developer finds the time to fix the outstanding issues, running the > test suite in a development environment should catch most (if not all) > of them. If there is no test suite, the developer is likely to be out > of luck anyway, IMHO. > >> > Screwing up the code and then hiding the results is NOT maintaining BC! > Apparently, the inclusion of E_STRICT to E_ALL wasn't supposed to screw > up anything.
Incremental changes from one version to the next may work for some people. The problem is bringing Pre-5.2 code forward so that it can reliably co-exist with already 'fixed' code. Many of the ISP's who tried simply switching their shared hosting to 5.4 found that so many sites simply stopped working that they had to revert the change. It is not 'developers' who have to find the time to make legacy code work on current servers ... it's users who have no idea even where to start! That their site is simply producing a white screen is not a help so perhaps the 'defaults' would be better off in favour of the unsophisticated user rather than something that pleases developers? Not that it helps anyway since distributions all throw their own two pennies in, and the 'suggested fixes' fail because the files are not where we tell them. That is if the hosting company even allow access. -- 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
