Re: Re: cvs: ZendEngine2(PHP_5_2) / zend_compile.czend_object_handlers.c /tests bug37632.phpt
| From: | Steph Fox | Date: | Wed, 31 May 2006 02:14:49 +0000 |
| Subject: | Re: Re: cvs: ZendEngine2(PHP_5_2) / zend_compile.czend_object_handlers.c /tests bug37632.phpt | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-23806@lists.php.net to get a copy of this message | ||
Now if we were _really_ sneaky, we'd make E_DEVEL visible in 'lint mode' only...
At 03:02 PM 5/30/2006, Marcus Boerger wrote:Now that's why I suggested E_DEVEL for 'advisory' issues. The problem is that E_STRICT, according to the manual and most of the dev team, is only there for 'real' deprecation issues. - Stephwhatever the patch looks like, it is a change from 5.0.0's E_STRICT to a E_COMPILE_ERROR and actually fixes another problem. This raises an interesting question. How long must we wait until we can follow the E_STRICT idea and change a specific E_STRICT into a fatal error. Must it be until eternity?E_STRICT doesn't mean that those warnings will become errors down the road. It just enforces best practices, and some might deprecate and some might not...Andi