php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #52517 E_COMPILE_WARNING is not
Submitted: 2010-08-02 18:51 UTC Modified: 2010-08-17 21:55 UTC
From: david at grudl dot com Assigned: kalle (profile)
Status: Closed Package: Compile Warning
PHP Version: 5.3.3 OS:
Private report: No CVE-ID: None
View Developer Edit
 [2010-08-02 18:51 UTC] david at grudl dot com 
Description:
------------
E_COMPILE_WARNING is the only run-time error not catchable by user-defined error handler function (via set_error_handler). I suggest change this behavior. 

Test script:
---------------
<?php

declare(foo='bar'); // throws E_COMPILE_WARNING

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-08-02 18:54 UTC] david at grudl dot com 
"run-time error" -> "runtime warning"
 [2010-08-16 21:42 UTC] kalle@php.net
-Status: Open +Status: Closed -Assigned To: +Assigned To: kalle
 [2010-08-16 21:42 UTC] kalle@php.net 
The declare struct have meaning for the script at compile time, not execution time hence its an E_COMPILE_WARNING.
 [2010-08-17 18:43 UTC] david at grudl dot com 
It is not about declare struct, it is about handing warnings & notices by user-handler (and logging them e.g.). I am unable to catch and log this warning. Please re-open this issue.
 [2010-08-17 20:20 UTC] kalle@php.net 
Yes it is, as declare is evaluated at compile time, not execution time hence its not possible to catch the warning anyway as its thrown before the executor is hit.
 [2010-08-17 21:47 UTC] david at grudl dot com 
There is not difference between compile time or execution time. Compilation is invoked by "include" or "require" or "eval" in run time. So statements "require" throw E_COMPILE_WARNING and you cannot handle them using user-defined error handler.
 [2010-08-17 21:55 UTC] kalle@php.net
-Block user comment: N +Block user comment: Y
 [2010-08-17 21:55 UTC] kalle@php.net 
There is alot of difference between them. Using your example code the declare statement is hit at compile time, so before the the executor is triggered that hooks into the error handler the warning is already thrown. Same things goes for includes, although they are as you rightly put it, executed at runtime. This is  how the Zend Engine is designed and not going to change.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Tue Oct 08 10:01:27 2024 UTC