Clint Priest wrote:
So I think we should try to keep PHP behavior unified and avoid
behavior-modifying switches as much as possible.
I agree all of that would suck, but would it suck less than the alternatives for
the most people involved?
E_STRICT is bad enough and is one of the switches you would have to test
everything against. But the main problem is that there is nothing in the
historic code base that easily allows someone to identify which version of PHP
IS required to run it? THIS is where move code forward to comply with the
existing 'E_DEPRECATED/E_STRICT' is a minefield, so adding yet another major
rework seems to be a step too far?
Now if someone could come up with a third party tool that reads an application
... identifies all of the problems ... and at least offer pointers to fix them ...
--
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
