On 16/07/14 23:12, Andrea Faulds wrote: > As I’ve explained earlier, letting them choose to make this fatal would be a > horrible, horrible idea.
This is no worse than the current mess created by E_STRICT ... we wither have to spend days reworking the code to respect E_STRICT ... or we switch it off. For legacy systems it simply HAS to be switched off and on the whole the code works. I'm with Zeev that the default at this point in time should be 'off' which is what E_CAST provides. I can understand your concern over third party libraries forcing it on - we have exactly the same arogance with E_STRICT - so we need at least a litle cooperation, rather than someone dictating that a new way of working is the only way ofrward. -- 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
