Gustavo Lopes wrote:
Second, E_STRICT exists to encourage good OOP practices. There is a lot of code
that generates E_STRICT that does what it was intended to do (ask Lester). By
definition, code that's not supposed to generate E_STRICT messages but does is
buggy, but the fact that some code raises an E_STRICT does not signal, by
itself, a bug.
And in hindsight I'd say this was one of the worst decisions made in the past
!!!
Simply switching something off just to make code work again is just wrong how
ever you look at it. This 'strict' stuff should have been handled with a bit
more intelligence such as providing a report as to non-compliant code which
picks up all the 'style differences' rather than having to work through layer
after layer of errors. My converted code is messy and does now need a 'style
tidy' clean-up. And I'm still not happy that what I AM doing the right things
anyway!
How many of the major PHP user projects ARE currently strict compliant? And how
many are still requiring E_STRICT switched off in PHP5.4?
--
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
