Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91191
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.51 as permitted sender)
To: =?UTF-8?Q?Fran=c3=a7ois_Laupretre?= <francois@php.net>,
 Internals <internals@lists.php.net>
References: <56A3A01F.1020500@php.net> <56BB4A5F.3060906@php.net>
Message-ID: <56BC29C8.9070308@gmail.com>
Date: Wed, 10 Feb 2016 22:27:20 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56BB4A5F.3060906@php.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Generalize support of negative string offsets
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I just added support for '[]' on strings and '{}' to the PR.
> 
> Examples :
> 
> $string[] = 'a'; // equivalent to : $string[strlen($string)]
> 
> $string{} = 'a'; // For consistency

That's probably not a good idea, and certainly is not good for the RFC -
the patch now does two unrelated things.

> This is not strictly in the scope of negative offsets. So, if you think
> it must be part of a separate RFC, I will remove it.

Yes, I think so. And I also thing it is a bad idea. We already have a
way to add stuff to the string - it's .= operator. Adding another weird
way to do it IMO is not good.

-- 
Stas Malyshev
smalyshev@gmail.com