Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85274
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPwsocHjoHVuBT8g=r3e-rG9W0cibEdXOxKzHPkGSaZwG7_NeQ@mail.gmail.com>
References: <CAAn=CzWySWQU1D93WA7L2eHvd31zogekEHmDUOsN7P6kBK4VrA@mail.gmail.com>
	<550B39AA.2090706@garfieldtech.com>
	<CAPwsocHjoHVuBT8g=r3e-rG9W0cibEdXOxKzHPkGSaZwG7_NeQ@mail.gmail.com>
Date: Fri, 20 Mar 2015 11:40:17 +0000
Message-ID: <CAAn=CzXAttDzUXuodVw=S90U5Kybr=wXumKACL+MfeK6FoxbXQ@mail.gmail.com>
To: Leigh <leight@gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a1135e9a8d5953c0511b6c7ba
Subject: Re: [PHP-DEV] RFC - Array slice syntactic sugar
From: bowersbros@gmail.com (Alex Bowers)

--001a1135e9a8d5953c0511b6c7ba
Content-Type: text/plain; charset=UTF-8

>
> I've tried implementing python style slice on both strings and arrays in

the past (I don't seem to have an existing branch with it in any more
> though it seems). The biggest problems I hit were regarding the syntax, the
> functionality itself worked.


If you've got a link to your messaging thread, I'd love to read it. Thanks

Colons caused problems with ternary operators in the lexer, and I had an
> issue with commas too, but I forget what it was. Of course these might have
> been resolvable, but I didn't put too much effort into it.


Could this not be mitigated by adding a new token like T_COLON to be used
to match this use case?

--001a1135e9a8d5953c0511b6c7ba--