Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84170
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.177 as permitted sender)
MIME-Version: 1.0
References: <885a29db28bc96b2d3cd2ac96907e39f@mail.gmail.com>
Date: Mon, 02 Mar 2015 15:10:49 +0000
Message-ID: <CACwt+JdL3YUQWHP04HOHHeE1=B98d8wgKT2VquWRJrEzmTfTXg@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0112cbfc9fe2b205104f9f98
Subject: Re: [PHP-DEV] Question/comment about the Array to String conversion RFC
From: patrickallaert@php.net (Patrick ALLAERT)

--089e0112cbfc9fe2b205104f9f98
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Le lun. 2 mars 2015 =C3=A0 15:24, Zeev Suraski <zeev@zend.com> a =C3=A9crit=
 :

> All,
>
>
>
> https://wiki.php.net/rfc/array-to-string (which I voted yes to) deviates
> from our guidelines of deprecating features first, and removing them
> later;  It=E2=80=99s addressed in the RFC =E2=80=93 but I=E2=80=99m a bit=
 worried that this opens
> the door to jumping from any sort of notice/warning into errors or remove=
d
> features without any deprecation phase.
>
>
>
> In comparison, in Nikita=E2=80=99s RFC for removing E_STRICT =E2=80=93 th=
ere aren=E2=80=99t any
> proposed =E2=80=98jumps=E2=80=99 to E_RECOVERABLE_ERROR that don=E2=80=99=
t first go through
> E_DEPRECATED.
>
>
>
> Should we not go through this deprecation cycle, even if may feel anxious
> to get rid of this behavior?
>

I'm all for deprecating before it gets removed (especially since I voted
"no" to that).

Patrick

--089e0112cbfc9fe2b205104f9f98--