Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23498
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:in-reply-to:references:mime-version:x-priority:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
	b=QjerNtsyVoB2AZQVyZUKctyVtET+L1uCOr585f3SC0vVo4UOrjuFtTF9AnnhwxL9POiixgoBGz3orRMtMfQqTedWiGHrp3orHqoNELFLQG1r6gN/tmpRnWY7K8wY6ohvJr8kG+mA+K51adIpxUUFDs6IRdHN3brZijQIZoAuVwo=
In-Reply-To: <13310440138.20060517015036@marcus-boerger.de>
References: <6C67DAD9-B812-415A-BFD6-A4E963371551@prohost.org> <13310440138.20060517015036@marcus-boerger.de>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <4F3C6065-92F4-494F-88C6-B6FCB0E51296@prohost.org>
Cc: PHP Internals List <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
Date: Tue, 16 May 2006 20:05:18 -0400
To: Marcus Boerger <helly@php.net>
Sender: Ilia Alshanetsky <iliaal@gmail.com>
Subject: Re: [PHP-DEV] Flamewar Summary
From: ilia@prohost.org (Ilia Alshanetsky)


On 16-May-06, at 7:50 PM, Marcus Boerger wrote:

> Hello Ilia,
>
> Wednesday, May 17, 2006, 1:26:37 AM, you wrote:
>
>> Inclusion of E_STRICT and E_RECOVERABLE_ERROR into E_ALL
> +1
> While doing all the stuff we wanted for 5.2 we also added
> E_RECOVERABLE_ERROR. This includes stuff that was E_ERROR before
> hand. And right now we didn't even start to systematically convert
> all error modes in the extension directory as we started to do in
> HEAD.
>

This can stay as it does not impact on the operation of existing  
application and is actually required, otherwise previously fatal  
errors will be bypassed.

> That said you most likely have to fix your error_reporting anyway or
> just don't care at all since you use settings that just work yor you.
>

Even if you were to release a new version of software today in  
anticipation of a the 5.2 release few months down the road most of  
your users will still use old versions while their ISP may have  
already upgraded their PHP.


> An argument i heared was that some applications that deal with
> error_reporting might get into trouble with this. I have a solution to
> that: we simply revert all the engine changes, or even better simply
> rebranch 5.1.4 again and do not do any progress other than fixing bugs
> and focusing on PHP 6.0.

I don't think anyone is suggesting that we revert everything, but we  
do need to work on minimizing the impact of our changes on our users  
in minor releases.


Ilia Alshanetsky
Advanced Internet Designs Inc.
ilia@prohost.org