Re: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2(PHP_5_3) / zend_API.c zend_API.h php-src/ext/standard type.c
| From: | Lukas Kahwe Smith | Date: | Fri, 01 Feb 2008 22:15:08 +0000 |
| Subject: | Re: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2(PHP_5_3) / zend_API.c zend_API.h php-src/ext/standard type.c | ||
| References: | 1 2 | Groups: | php.cvs php.internals |
| Request: | Send a blank email to internals+get-35081@lists.php.net to get a copy of this message | ||
On 01.02.2008, at 23:05, Pierre Joye wrote:
2008/2/1 Marcus Boerger <helly@php.net>:Yes .. I think for PHP we should follow these rules: 1) No fatal errors that are not fatal for the engine 2) throw E_STRICT for anything that makes a CS prof commit suicide PHP is about solving real world problems and not creating problems that are not there (making on fatal things fatal is creating a non existant problem). if people want to do the right thing in terms of CS they enable E_STRICT .. and if they want E_STRICT to be fatal they can create an error handler that does that for them. regards, LukasCrosspost, hopefully silencing this issue for 5.* AND 6 will have an E_WARNING or even an E_ERROR on this.What are the gains? What are the real reasons behing strictness? I really get annoying by adding fatal errors all around for no technical reasons. A fatal error means the engine is getting foo bared and can't do anything sane but leaving.