On Sun, Feb 3, 2013 at 2:50 PM, Rasmus Lerdorf <ras...@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 > >
