Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65583
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <510EBF98.4060900@lerdorf.com>
References: <CAOfzkkz3DC+aVb4c73QHGRzZv=1z=nG4uexdJh2n8h3ATGBBOA@mail.gmail.com>
	<CAEZPtU6UdX4uyR7tLomi==DNbmJduHoxa=qmb+dd2bJQKcoxjw@mail.gmail.com>
	<CAOfzkkwQNKRrX+MQ3JutkVWmHsCLZetJMp7AubA52E+=MSCcXw@mail.gmail.com>
	<510EBF98.4060900@lerdorf.com>
Date: Sun, 3 Feb 2013 15:48:21 -0500
Message-ID: <CAL+t6cFmnw=Ok4=R33e-zVAxSqR0g8dd4m=pQ=duE9p7_X_Sjg@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Karoly Negyesi <karoly@negyesi.net>, "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d043bdf38d1acb004d4d8185d
Subject: Re: [PHP-DEV] Proposal for serious BC compatibility aka language versioning
From: theanomaly.is@gmail.com (Sherif Ramadan)

--f46d043bdf38d1acb004d4d8185d
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Feb 3, 2013 at 2:50 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> On 02/03/2013 11:44 AM, Karoly Negyesi wrote:
> > Well, either I misunderstood the policy or it's broken. Here are some
> > (note: please do not argue whether these are more correct than before,
> > they very well might be but they broke backwards compatibility):
> >
> > For example, in 5.4 array_diff_assoc began to throw a notice when
> > casting to string.
> >
> > Again in 5.4, using a string offset against a string throws a warning.
> > It wasn't doing that before.
>
> We do not consider a change in warnings/notices a BC break. I realize
> for certain test frameworks and custom error handlers it could break
> things if they are expecting a specific warning or lack of warning, but
> the code itself behaves exactly as it did before and as such there is no
> BC break.
>

I for one think this point needs to be communicated a lot more clearly,
because when I attempted to introduce a patch that would throw E_DEPRECATED
warning for mcrypt last year I was told it could not be merged in 5.4 since
it would cause a BC break. Later someone else disagreed with that. So
clearly not everyone seems to be inline.

</my two cents>


>
> -Rasmus
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--f46d043bdf38d1acb004d4d8185d--