Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84168 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21048 invoked from network); 2 Mar 2015 14:24:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2015 14:24:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 74.125.82.178 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 74.125.82.178 mail-we0-f178.google.com Received: from [74.125.82.178] ([74.125.82.178:34345] helo=mail-we0-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F1/A0-14834-F8274F45 for ; Mon, 02 Mar 2015 09:24:16 -0500 Received: by wesq59 with SMTP id q59so33675327wes.1 for ; Mon, 02 Mar 2015 06:24:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=JEZgtW5J4Cb/pO10k9/+wj2CaOvCWcoZSrfbia0mocE=; b=RjP4RUwefY3IDwCwOleJ2vCRUF0b08NFO5bPnFn5+flVrY9u62K0JPnNRReU+fJgt6 qZAM/xCv4kRgmggtrBO5cqKsKtrAdY4geZtm5NENGjG9mMVADyRiXDOpTz2qDXONQbZY zBMwI1+Ymqsi9MLvN/N6n8vlRygl5kWmMjVJ+Pgq8zLnpHc63O3YFE1z6LipksRaFDOm V8H3DOtq9sgfEowEAougwzBsUL5P4dsekvRrbrc8xfOFutH1rfXYpyFA+W5y/dWYc4bn l1ldZDt8B12dAiEP/kzDv2fvjoOuaYeJYT2eFbQ1O1saLTXLCryGEaYkb3gi/lie1Z1u EpXA== X-Gm-Message-State: ALoCoQk3rYPiy42rVkg3OOBMzURWxqWSDpP8FCJ0b4HZrRwJyKsv/B+CkZ+eIICHwhpZGlSLtXSrB8/eGoNCfUFJiolA0ZPY4sTFOcm+RAwJy6o7cGKnggIIP4SGDBWh5Jr4Ppb59sfbJGXW6g+gbN5S7JmUOcStyA== X-Received: by 10.194.200.229 with SMTP id jv5mr6254711wjc.59.1425306249960; Mon, 02 Mar 2015 06:24:09 -0800 (PST) MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdBU9IwWWKAS5IRVRU2bnnVCy5PCDA== Date: Mon, 2 Mar 2015 16:24:09 +0200 Message-ID: <885a29db28bc96b2d3cd2ac96907e39f@mail.gmail.com> To: PHP internals Content-Type: multipart/alternative; boundary=047d7bb70b68b9affe05104ef845 Subject: Question/comment about the Array to String conversion RFC From: zeev@zend.com (Zeev Suraski) --047d7bb70b68b9affe05104ef845 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 w= orried that this opens the door to jumping from any sort of notice/warning into errors or removed features without any deprecation phase. In comparison, in Nikita=E2=80=99s RFC for removing E_STRICT =E2=80=93 ther= e aren=E2=80=99t any proposed =E2=80=98jumps=E2=80=99 to E_RECOVERABLE_ERROR that don=E2=80=99t = first go through E_DEPRECATED. Should we not go through this deprecation cycle, even if may feel anxious to get rid of this behavior? Zeev --047d7bb70b68b9affe05104ef845--