Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84547
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAOsHV+sF67RkS7p9HHrMdaDxRrp_m00mMBivwvDeJ8htOjKUtg@mail.gmail.com>
References: <CAOsHV+uuVvyg+gjLoNkn+DxqTS6C4K4T5cPGJArW=ERBFeyPBA@mail.gmail.com>
	<CAF+90c-hwVxCaVTX6_yt4LT5wEi5Xf-2J+aDROeW=8148YicMg@mail.gmail.com>
	<CAOsHV+u+pHiDcVjbaOpjcmjEm+9r1GRvprLm2oQwuYFprhXfiw@mail.gmail.com>
	<CAOsHV+sF67RkS7p9HHrMdaDxRrp_m00mMBivwvDeJ8htOjKUtg@mail.gmail.com>
Date: Wed, 11 Mar 2015 15:49:38 +0100
Message-ID: <CAF+90c-ZhHxf3wRz0mPiF-sZNU7Z3QGLQS3ugG+0d8qimmvbbw@mail.gmail.com>
To: marcio3w@gmail.com
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bfcf00061d50c051104606b
Subject: Re: [PHP-DEV][RFC][VOTING] Context Sensitive Lexer
From: nikita.ppv@gmail.com (Nikita Popov)

--047d7bfcf00061d50c051104606b
Content-Type: text/plain; charset=UTF-8

On Mon, Mar 9, 2015 at 6:47 AM, Marcio Almada <marcio.web2@gmail.com> wrote:

> Hi,
>
> Just passing by to announce I already have a working version of the new
> patch: https://github.com/php/php-src/pull/1158
>
> The patch is 100% compatible with the proposed one with the advantages:
>
>    - Has no regression or forward compatibility risks and is highly
>    predictable
>    - Has an very small footprint compared to the previous attempt involving
>    a pure lexical approach
>    - Is highly configurable, to make a word semi-reserved you only have to
>    edit a single inclusive list in a parser rule.
>    - Requires a single compile time check
>
> More than ever, I'd like to advice voters to vote for the feature as the
> new implementation is already on it's way. There still some work to be
> done, please refer to the task list on the pull request to see what still
> needs to be done.
>
> It would be nice to have the new patch reviewed too.
>

The new implementation does indeed look much nicer :) The only open
question left is how you want to deal with ext/tokenizer support. Can you
clarify your plan regarding that?

Also, is this vote about the new implementation now?

Nikita

--047d7bfcf00061d50c051104606b--