Bug #42098 [Nab]: E_STRICT doesn't trigger __autoload()

Edit report at https://bugs.php.net/bug.php?id=42098&edit=1 ID: 42098 Updated by: tony2001@php.net Reported by: nicolas dot grekas+php at gmail dot com Summary: E_STRICT doesn't trigger __autoload() Status: Not a bug Type: Bug Package: Scripting Engine problem Operating System: * PHP Version: 5.2.3 Block user comment: N Private report: N New Comment: See detailed answer in bug #54054. Previous Comments: ------------------------------------------------------------------------ [2012-12-28 10:55:04] nicolas dot grekas+php at gmail dot com The error codes concerned by this bug are the ones used in Zend/zend_compile.c: E_STRICT, E_DEPRECATED, E_NOTICE, E_WARNING, E_ERROR, E_CORE_ERROR, E_COMPILE_ERROR and E_COMPILE_WARNING. So virtually no error code is safe. A workaround strategy at source code level would be to stack errors at compile time, then trigger them just when compile time is over. Is it possible? Anyone as a better idea? ------------------------------------------------------------------------ [2012-12-27 09:41:18] nicolas dot grekas+php at gmail dot com Related To: Bug #54054 ------------------------------------------------------------------------ [2011-09-14 11:51:47] phil at propcom dot co dot uk This is related to https://bugs.php.net/bug.php?id=54054&edit=2 which I have just commented on proving some, hopefully, sane example code. ------------------------------------------------------------------------ [2010-05-25 11:12:20] i at walkinraven dot name I think autoload will not work in exception_handler or error_handler, that is the problem. ------------------------------------------------------------------------ [2007-08-17 23:08:16] tony2001@php.net >Ah ah ! You play with words :) No, he just said the same thing in other words. >The first time, you said : >- "Only execute time errors can be caught with user error handler.", >and now: >- "during compile -> autoload wont be triggered" There are two stages: 1) compile; 2) execute. Compile-time errors cannot be caught, only execute-time errors can be. >But that's still a bug for me in this case. My workaround does >exactily what PHP internals should do automagically, nothing more ! This is how the things work. ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=42098 -- Edit this bug report at https://bugs.php.net/bug.php?id=42098&edit=1