Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101902 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72924 invoked from network); 22 Feb 2018 20:38:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Feb 2018 20:38:18 -0000 Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.217 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.217 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.217] ([81.169.146.217:35819] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 26/A0-01511-63A2F8A5 for ; Thu, 22 Feb 2018 15:38:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1519331892; s=strato-dkim-0002; d=kelunik.com; h=Content-Transfer-Encoding:Content-Type:Cc:To:Subject:Message-ID: Date:From:References:In-Reply-To:X-RZG-CLASS-ID:X-RZG-AUTH; bh=bvrqq9p/pT0FVM9BTd3ZdjTvwOYld2T1Cu9rzElPEVE=; b=RziwNw7WYYPCawtfeCqdYZYiKa0XEDjX+z1N7cH/K0KJiYu5YTZba4la789oAVcnbl udOv4VjkTUoVX/WmzIhimVtcPz6b1j6UIj1Lwtr/7gdodvm6x0tTwzXa/dM2qyRBb4Vj L9FxTlzCJ4T68NcabQkSXUVOw90cXHY0EFWuBYlT8FjBX6e3KfuuuNa7zYCRYF3k26Ox b9UljiHql9zNqngDCAXHgQhP06fVQKsTmkEcK+pKW4N807RUDI+gZduvxupAovobLDjq ZIC/OQ45Uss1oRF+ScuuThBWcriQ7d5vimLLhpcJ25MBx65VCe8lrjZPhx3A7hevhy3j 09WA== X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mlsGbEv0XHBzMIJSS+jKFAZe0ePnmPzZdHds4= X-RZG-CLASS-ID: mo00 Received: by mail-wm0-f49.google.com with SMTP id t74so790885wme.3 for ; Thu, 22 Feb 2018 12:38:12 -0800 (PST) X-Gm-Message-State: APf1xPA7Hjo4A8F9JsDPwnvQg2334WPIXLYzx1w4NC7aWvoOvB/io1Jm yoyq8sD64OYPmk4HkqjdMWR28VKL5erosRpPIWc= X-Google-Smtp-Source: AG47ELsa/psvtoCaOUflVDZwsgKovXqju8j+Qy193aEtdhrMydVmPLdtcXdjKhg6DhZgccJSY2d16Oo/7WQcbyyEWXs= X-Received: by 10.28.13.18 with SMTP id 18mr387582wmn.112.1519331892080; Thu, 22 Feb 2018 12:38:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.176.164 with HTTP; Thu, 22 Feb 2018 12:38:11 -0800 (PST) In-Reply-To: References: Date: Thu, 22 Feb 2018 21:38:11 +0100 X-Gmail-Original-Message-ID: Message-ID: To: =?UTF-8?Q?Pedro_Magalh=C3=A3es?= Cc: PHP internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: [RFC] [Discussion] Arrays starting with a negative index From: me@kelunik.com (Niklas Keller) Hey, "Will no longer produce any output." in the BC example is wrong, it will produce a notice due to an undefined index then. > NOTE: If accepted, during the deprecation phase the following E_DEPRECATE= D notice would be emitted in cases where the behavior will change: I guess that means also $a[-3] =3D true; $a[] =3D false; will emit a deprecation notice? Regards, Niklas 2018-02-22 18:38 GMT+01:00 Pedro Magalh=C3=A3es : > On Tue, Feb 13, 2018 at 8:03 PM, Pedro Magalh=C3=A3es w= rote: > >> Hi internals, >> >> I want to bring up this RFC once again given that now seems to be the >> right timing for it. I have previously canceled the vote when I initiall= y >> proposed this to land on 7.2 which was seen as too big of a BC for a min= or >> version. On a second attempt targeting 8.0 I have also canceled the vote= as >> the inclusion of a deprecation notice in cases where the behavior will >> change warranted further discussion. >> >> To address these issues, the current version of the RFC will have 2 >> separate votes: >> - Introduce the new behavior on 8.0 >> - Introduce a deprecation notice on 7.3 >> >> For those not familiar with the RFC, the general idea is that currently, >> any array that has a number n as it's first numeric key will have for it= 's >> next implicit key either n+1 if n >=3D 0 or 0 if n < 0. This RFC propose= s to >> make this consistent by always using n+1 regardless of the sign of n. >> In code: >> $a[-2] =3D true; // Current: Key is -2, RFC: Key is -2 >> $a[] =3D true; // Current: Key is 0, RFC: Key is -1 >> $a[] =3D true; // Current: Key is 1, RFC: Key is 0 >> >> I invite you to read the full RFC: https://wiki.php.net/rfc/ >> negative_array_index and bring up any issues you see with the current >> version before the voting period starts. >> >> Looking forward for any feedback. >> >> Regards, >> Pedro Magalh=C3=A3es >> > > Hi internals, > > I'd like to open the voting for this RFC in 5 days (27/2). > Please bring up any feedback you may have about it before the voting peri= od > starts. > > Thanks in advance, > Pedro Magalh=C3=A3es