Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23806
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <06f301c68457$ffa0b060$6602a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Marcus Boerger" <helly@php.net>,
	"Christian Schneider" <cschneid@cschneid.com>,
	"Andi Gutmans" <andi@zend.com>
Cc: "Antony Dovgal" <antony@zend.com>, <internals@lists.php.net>,
	"Hannes Magnusson" <bjori@php.net>
Date: Wed, 31 May 2006 04:14:49 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: cvs: ZendEngine2(PHP_5_2) / zend_compile.czend_object_handlers.c /tests bug37632.phpt
From: steph@zend.com ("Steph Fox")

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:
>>>   whatever 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...
>
> 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.
>
> - Steph
>
>> Andi
>