Re: Feature proposal
| From: | Wojtek Meler | Date: | Tue, 22 Jul 2003 18:39:27 +0000 |
| Subject: | Re: Feature proposal | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-3565@lists.php.net to get a copy of this message | ||
Ken Tossell wrote:
But often errors/warnings are *not* bugs. Or maybe you don't want to show your users the ugly messages from something like include -- if (!@include 'foo.php') die('Couldn\'t..');Well it is true. Sometimes it is needed and that's why this functionality is turned off by default. But sometimes you are searching for hours something that is little '@' before call to undefined function - script crashes and you don't know where. All what you have is 'grep' on all sources, filter email adresses etc. http://www.php.net/manual/en/language.operators.errorcontrol.php : *Warning* Currently the "@" error-control operator prefix will even disable error reporting for critical errors that will terminate script execution. Among other things, this means that if you use "@" to suppress errors from a certain function and either it isn't available or has been mistyped, the script will die right there with no indication as to why.
http://strony.wp.pl/wp/wmeler/error_suppression.patch.txtThis account has funny restrictions - try go through http://strony.wp.pl/wp/wmeler/.