On Fri, 6 Oct 2006, Edin Kadribasic wrote: > Edin Kadribasic wrote: > > Stanislav Malyshev wrote: > > > > The vote is should OO strictness (fatal error on changing function > > > > arguments in derived classes in this case) be removed or kept. > > > > > > I think fatal error should be definitely removed or the rules be at least > > > relaxed sufficiently to accomodate for PHP flexibility - e.g., () should > > > be allowed to be overriden with ($a, $b, $c), etc. In light of technical > > > difficulty to implement sufficiently flexible cheks, I would not mind > > > removing them altogether or demoting them to very low priority notice. > > > > Yes, it was my opinion as well that E_NOTICE would be the most appropriate > > choice here. > > Hate to have to reply to myself, but to clarify. > > I believe that most OO "strictness" fatal errors should be demoted to notices.
This is why we have E_STRICT, not? :) regards, Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
