#50897 [Bgs]: Require() problem with E_STRICT

ID: 50897 User updated by: frederic dot hardy at mageekbox dot net Reported By: frederic dot hardy at mageekbox dot net Status: Bogus Bug Type: Scripting Engine problem Operating System: * PHP Version: 5.*, 6 New Comment: I'm confirm that. With error level set to E_STRICT in php.ini, the warning is displayed. Previous Comments: ------------------------------------------------------------------------ [2010-02-01 13:51:54] dmitry@php.net A class in PHP may be declared at compile time or at run time. As result the warning is also emitted at compile or run time. It's clear that compile time declarations aren't affected by error_reporting() function and use setting from php.ini. So in your examples the error isn't lost, but just hidden by settings in your php.ini. ------------------------------------------------------------------------ [2010-02-01 13:29:28] frederic dot hardy at mageekbox dot net lol :). So there is an another problem, __construct() seems to be not checked like other method... It seems to me that there is lot of inconsistency with E_STRICT and method signature checking. ------------------------------------------------------------------------ [2010-02-01 13:08:06] jani@php.net If you feel it's a problem, don't put E_STRICT in your error_reporting.. ------------------------------------------------------------------------ [2010-02-01 12:27:11] frederic dot hardy at mageekbox dot net Why the notice should be output in all cases ? It's not a problem if b::test() has a signature wich is different from a::test(). If it's a problem, what is the interest of extends b from a, or more globaly, what is the interest of inheritance if you can not override method with different signature ? ------------------------------------------------------------------------ [2010-02-01 12:21:08] jani@php.net And the notice should be output in all cases.. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/50897 -- Edit this bug report at http://bugs.php.net/?id=50897&edit=1