Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91037
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <56A3A01F.1020500@php.net>
References: <56A3A01F.1020500@php.net>
Date: Sun, 31 Jan 2016 23:03:04 +0100
Message-ID: <CAF+90c-rh5uss4xTjbvvjr6PO5iAYaQ=DQRbVNr+h1kMm8HW9A@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@php.net>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114e7e30c3c3e0052aa86ea2
Subject: Re: [PHP-DEV] [RFC] Generalize support of negative string offsets
From: nikita.ppv@gmail.com (Nikita Popov)

--001a114e7e30c3c3e0052aa86ea2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 23, 2016 at 4:45 PM, Fran=C3=A7ois Laupretre <francois@php.net>
wrote:

> Hi,
>
> Starting discussion about https://wiki.php.net/rfc/negative-string-offset=
s
>
> Please read and comment.
>

Just dropping by with a +1 on this proposal. Consistent support is always
good.

The only concern I have is that support of negative indexing will break
symmetry with (proper) arrays, where we cannot support negative indexing.
I.e. this may lead to "Why can I write $str[-1] to get the last character
in a string, but not $array[-1] to get the last element in an array?"
However this is unlikely to be a significant issue. (I do however play with
the thought of reutilizing the obsolete {} indexing syntax to act as offset
indexing instead.)

Nikita

--001a114e7e30c3c3e0052aa86ea2--