Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91185
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.161.172 cause and error)
MIME-Version: 1.0
In-Reply-To: <56BB4A5F.3060906@php.net>
References: <56A3A01F.1020500@php.net>
	<56BB4A5F.3060906@php.net>
Date: Wed, 10 Feb 2016 14:49:51 +0000
Message-ID: <CA+kxMuQ2ez0TAXDciW39BxdscQe_xGGJ7WxpoenFpdV3S0bSAw@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@php.net>
Cc: Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Generalize support of negative string offsets
From: danack@basereality.com (Dan Ackroyd)

On 10 February 2016 at 14:34, Fran=C3=A7ois Laupretre <francois@php.net> wr=
ote:
> Hi,
>
> I just added support for '[]' on strings and '{}' to the PR.
>
> Examples :
>
> $string[] =3D 'a'; // equivalent to : $string[strlen($string)]
>
> $string{} =3D 'a'; // For consistency

Unless I'm missing some subtleties, that appears to just be a more
confusing version of string concatenation.

$string[] =3D 'a';

is equivalent to :

$string .=3D 'a';

Is that correct?

> This is not strictly in the scope of negative offsets. So, if you think i=
t
> must be part of a separate RFC, I will remove it.

It seems unnecessary. Unless I've misunderstood what it does, it's
just a complete duplication of functionality we already have (, in a
way that is likely to confuse people, imo) and having duplicate
functionality is not so good.

At the very least it needs to be part of a separate vote option - but
my opinion is that it's not needed at all, and should be left out
entirely.

cheers
Dan