Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85229
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <28871A37-A2F8-465F-8717-A116B8AA78C7@zend.com>
References: <885a29db28bc96b2d3cd2ac96907e39f@mail.gmail.com>
	<077401d06268$2b597c30$820c7490$@php.net>
	<CA+kxMuRG7RV74uD=pJxB2M3LS9Ty1xB-+TN_ddMpYg4xgtjpwA@mail.gmail.com>
	<28871A37-A2F8-465F-8717-A116B8AA78C7@zend.com>
Date: Thu, 19 Mar 2015 19:04:19 +0100
Message-ID: <CAF+90c9NDy-zDpZ-sT4VGXOx2T=71Fvh8Dkb1GZUhT=UhjGKpQ@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Dan Ackroyd <danack@basereality.com>, "francois@php.net" <francois@php.net>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bfceb405a17bf0511a807a3
Subject: Re: [PHP-DEV] Question/comment about the Array to String conversion RFC
From: nikita.ppv@gmail.com (Nikita Popov)

--047d7bfceb405a17bf0511a807a3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 19, 2015 at 6:49 PM, Zeev Suraski <zeev@zend.com> wrote:

> > On 19 =D7=91=D7=9E=D7=A8=D7=A5 2015, at 19:40, Dan Ackroyd <danack@base=
reality.com> wrote:
> >
> > You are being dumb here as well. We try to avoid breaking code in
> > point releases. This BC break can only be done at a major version.
>
> Technically, we're not allowed to move from from a working feature into a
> removed one without a deprecation phase.
>

I don't think this is true. There is no requirement for us to deprecate
something before we remove it. Deprecation is a courtesy to our users in
cases where a heavily used feature is being dropped.

Realistically most people consider E_NOTICE to be a higher error level than
E_DEPRECATED. If somebody is willing to suppress the notices this currently
generates, chances are very high that deprecations are suppressed as well.

I don't see any release process issues with dropping this without
deprecation. (But I'm still -1 on the change, because I don't see why we'd
suddenly want to change this one relatively unimportant notice to be fatal
while leaving everything else alone.)

Nikita

--047d7bfceb405a17bf0511a807a3--