Bug #66066 [Com]: opcache_compile_file partially execute file and output errors

Edit report at https://bugs.php.net/bug.php?id=66066&edit=1 ID: 66066 Comment by: Terry at ellisons dot org dot uk Reported by: geompse at gmail dot com Summary: opcache_compile_file partially execute file and output errors Status: Open Type: Bug Package: opcache Operating System: Debian 3.8.13 PHP Version: 5.5.5 Block user comment: N Private report: N New Comment: Geompse, this may be counter-intuitive behaviour, but this is PHP that we're talking about here :-) What you are trying to do is hitting artefacts of Zend engine constraints rather than OPcache ones. You will get into just the same sort of problems if you try to do an include __FILE__; if your file embeds statically declared functions or classes. The PHP bugrep system is a poor place to have this discussion. Why not post a Q to StackOverflow explaining what you are trying to do, and we can have the discussion on a forum more suited to this? If we distill out of that some specific issue that needs raising here, then there is more chance of it getting actioned that way. Terry Previous Comments: ------------------------------------------------------------------------ [2014-01-13 03:18:47] geompse at gmail dot com Terry, This may not be a "logical bug" but it is at least an undocumented behavior. To me, this is very misleading ("Fatal error" not fatal for the current script). Plus, combined with exception_handler this will do "weird shit". >> There should be an optional argument or configuration to disable both errors, or >> compile-scope error(s). See practical use, framework is designed for production usage. All errors are e-mailed, db-stored and eventually displayed. Any error is fatal (die). The function is doing what the documentation says it does. But it is doing more than that. Please correct either the function ("bug") or the documentation ("documentation problem"). Cordialement, Geompse ------------------------------------------------------------------------ [2014-01-12 15:57:23] Terry at ellisons dot org dot uk This is "Not a bug". What you are describing is the behaviour that we'd expect with PHP and OPcache, so why is it a bug? EG(function_table) already contains an entry for function coucou, so compiling any script with coucou in it will result in a "Cannot redeclare" error being thrown. ------------------------------------------------------------------------ [2013-11-08 16:18:00] geompse at gmail dot com Description: ------------ --- From manual page: http://www.php.net/function.opcache-compile-file "Compiles and caches a PHP script without executing it" --- As the documentation says, the script should not be executed (and it is not). But when trying to compile the current file, or an already included/required file, the function generate a Fatal Error and a Warning (wich can both by visually suppressed when using "@"). Practical use : updater script - overwrite files with new ones - force opcache recompilation The update is in the framework, and updates the framework. All already-included classes are already defined, and thus the compilation fail (or seems to fail, anyways it reports a failure). Test script: --------------- <?php error_reporting(E_ALL); ini_set('display_errors','On'); function coucou() { } echo 'Before'."\n"; opcache_compile_file(__FILE__); echo 'After'."\n"; ?> Expected result: ---------------- Before After Actual result: -------------- Before Fatal error: Cannot redeclare coucou() (previously declared in /root/compile.php:8) in /root/compile.php on line 8 Warning: Zend OPcache could not compile file /root/compile.php in Unknown on line 0 After ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=66066&edit=1