Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85225
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 74.125.82.43 as permitted sender)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
In-Reply-To: <CA+kxMuRG7RV74uD=pJxB2M3LS9Ty1xB-+TN_ddMpYg4xgtjpwA@mail.gmail.com>
Date: Thu, 19 Mar 2015 19:49:14 +0200
Cc: "francois@php.net" <francois@php.net>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <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>
To: Dan Ackroyd <danack@basereality.com>
Subject: Re: [PHP-DEV] Question/comment about the Array to String conversion RFC
From: zeev@zend.com (Zeev Suraski)

> On 19 =D7=91=D7=9E=D7=A8=D7=A5 2015, at 19:40, Dan Ackroyd <danack@baserea=
lity.com> wrote:
>=20
> 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 re=
moved one without a deprecation phase.

So why I agree with you it's a problem to just edit the RFC without getting a=
 wide OK for it after a vote has concluded, what's much worse is that so man=
y people voted Yes for an RFC that violated that principle, and not s single=
 person was bothered to even reply to a query about it.  Note that contrary t=
o what you said, a vote would have been equally required regardless of wheth=
er we follow our deprecation process, or violate it for no good reason.

You're right we won't be able to move to remove it in 7.x - but it's exactly=
 at the same level that we mustn't move to an error in 7.0.

Zeev=