Newsgroups: php.internals,php.qa
Path: news.php.net
Xref: news.php.net php.internals:36735 php.qa:64138
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.184 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=JZiOUlk8EwYy5+yomie3QnI5PV4DVbt4Tqo11rUYKtSTLXFILy6BVnxfJp1g6Egk3iIWijEq8hK0FJbrbXrwYDBb832ycVdkLDIuRQBDgT97VgZ8MznOl1qFnKAZCOpxWAJOdFcr+Pe4KdDP44c8FX+t/38KbBuw8Owz3KsDv2c=
Message-ID: <fe05d1540803311522h5c2b2adcqe17997fab903121e@mail.gmail.com>
Date: Tue, 1 Apr 2008 00:22:55 +0200
To: "=?ISO-8859-1?Q?Johannes_Schl=FCter?=" <johannes@php.net>
Cc: "Marcus Boerger" <helly@php.net>, "Derick Rethans" <derick@php.net>, 
	"Marco Kaiser" <marco.kaiser@gmail.com>, 
	"PHP Developers Mailing List" <internals@lists.php.net>, 
	php-qa@lists.php.net, "Ilia Alshanetsky" <ilia@prohost.org>
In-Reply-To: <1206998314.2941.6.camel@goldfinger>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <a2b4d2820803270125w1c167b3fmbd721458457f3643@mail.gmail.com>
	 <1124764115.20080327105033@marcus-boerger.de>
	 <47eb9d50.02e2660a.759d.2e19@mx.google.com>
	 <alpine.DEB.0.98.0803301729300.2627@kossu.ez.no>
	 <826883759.20080331171437@marcus-boerger.de>
	 <1206998314.2941.6.camel@goldfinger>
Subject: Re: [PHP-DEV] Re: [PHP-QA] BC break with php 5.2.6
From: pierre.php@gmail.com ("Pierre Joye")

On Mon, Mar 31, 2008 at 11:18 PM, Johannes Schl=FCter <johannes@php.net> wr=
ote:
> Marcus,
>
>
>  On Mon, 2008-03-31 at 17:14 +0200, Marcus Boerger wrote:
>  > Hello Derick,
>  >
>  >   it is a BUG FIX. Not fixing it means more people will turn it into a
>  > feature and we will never be able to remove it. Becuase next time you
>  > will say we cannot remove it in a minor version as by then you acciden=
tally
>  > rely on it yourself.
>  >
>  > We made a mistake! Lets stand up and admit we did. Probably I was invo=
lved
>  > in making that mistake, so sorry. Done.
>
>  I have to agree with Derick here we shouldn't add a fatal error within a
>  bug fix release at such a place. People (hosters...) tend to update
>  versions without checking all incompatibilities - since you don't expect
>  them and they want to get security issues fixed.
>
>  Yes, the previous behavior was wrong! Yes we shouldn't encourage people
>  do do that.
>
>  I'd propose making it an Warning or something in 5.2 and fixing it in
>  5.3.

E_DEPRECATED  is more appropriate.

--=20
Pierre
http://blog.thepimp.net | http://www.libgd.org