Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23827
Return-Path: <antony@zend.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 51767 invoked by uid 1010); 31 May 2006 14:24:44 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 51751 invoked from network); 31 May 2006 14:24:44 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 31 May 2006 14:24:44 -0000
X-PHP-List-Original-Sender: antony@zend.com
X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4)
Received: from ([80.74.107.235:38411] helo=mail.zend.com)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id 6F/08-07504-B27AD744 for <internals@lists.php.net>; Wed, 31 May 2006 10:24:44 -0400
Received: (qmail 14346 invoked from network); 31 May 2006 14:24:18 -0000
Received: from internal.zend.office (HELO ?127.0.0.1?) (10.1.1.1)
	by internal.zend.office with SMTP; 31 May 2006 14:24:18 -0000
Message-ID: <447DA723.9090108@zend.com>
Date: Wed, 31 May 2006 18:24:35 +0400
User-Agent: Thunderbird 1.5.0.2 (X11/20060420)
MIME-Version: 1.0
To: Derick Rethans <derick@php.net>
CC: Marcus Boerger <helly@php.net>,  internals@lists.php.net
References: <649570026.20060531004803@marcus-boerger.de> <Pine.LNX.4.62.0605310945460.3797@localhost>
In-Reply-To: <Pine.LNX.4.62.0605310945460.3797@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] E_STRICT
From: antony@zend.com (Antony Dovgal)

On 31.05.2006 11:46, Derick Rethans wrote:
> On Wed, 31 May 2006, Marcus Boerger wrote:
> 
>>   right now the fate of E_STRICT error messages is uncertain. A few
>> people think those should change to fatal after a reasonable amount of
>> time, is two years (e.g. 5.0.0) reasonable. A few even think a minor
>> version like 5.1 to 5.2 is enough but the majortiy (at least i guess
>> so) wants the change only on a major version change like 5.0 to 6.0.
>> 
>> Currently the manual says:
>> <manual>
>> 2048 E_STRICT (integer)  Run-time notices. Enable to have PHP suggest
>> changes to your code which will ensure the best interoperability and
>> forward compatibility of your code.  since PHP 5
>> </manual>
>> 
>> So the RFC goes: Extend the manual to specify that issues reported by
>> E_STRICT messages are most likely to become fatal errors in the next
>> major version.
> 
> I would say so, as long as we define major version as "6.0" here.

Yes.
So that E_STRICT notices introduced in 6.x will become E_FATALs only in 7.0 and so on.

-- 
Wbr, 
Antony Dovgal