Stas Malyshev wrote:
But with a strong warning that on a later version of PHP things WILL stop
>working altogether? More often now E_DEPRECATED is already switched off simply
Why again we must breaking people's working code?
Something I've been asking for years ;)
Bigger frameworks still designing for PHP5.3 is happening because 5.2 code still
works on 5.3 by hiding warnings, but fails on 5.4. They are trying to keep THEIR
users functional in the real world, and the real world is dragging it's feet
simply because the majority of users would not know what E_DEPRECATED means.
"They have had plenty of time to fix this" assumes that the people who wrote the
original code are still around TO fix it? I'm still finding live code that
originated in PHP4 days - using 'mysql_' - and works perfectly - on 5.2.
I have three options now ...
1/ Stick with a stack that will run their code
2/ Tell the customers they need to repair all their code
3/ Charge them for the time to repair the code for them
Many ISP's are simply opting for 1 because 2 can't happen on many accounts, and
there is not enough time available for 3 which most customers could not afford
anyway.
I've been forced to move sites from their exiting hosting simply because that
host HAS upgraded and I don't have time to fix all the problems on code for the
customer!
FINALLY sorted why everything was broken moving from Apache2.2 to 2.4 now I have
to work out the 'politically correct' fix for that :(
--
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
