Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84563
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.182 as permitted sender)
MIME-Version: 1.0
Reply-To: marcio3w@gmail.com
In-Reply-To: <CAF+90c-ZhHxf3wRz0mPiF-sZNU7Z3QGLQS3ugG+0d8qimmvbbw@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> <CAF+90c-ZhHxf3wRz0mPiF-sZNU7Z3QGLQS3ugG+0d8qimmvbbw@mail.gmail.com>
Date: Wed, 11 Mar 2015 14:55:16 -0300
Message-ID: <CAOsHV+vgdx8+tJ1BF-BgeuRgjOSVRSbjEXbZjYhxrDuXr05FPg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11340c688258bd051106f9c1
Subject: Re: [PHP-DEV][RFC][VOTING] Context Sensitive Lexer
From: marcio.web2@gmail.com (Marcio Almada)

--001a11340c688258bd051106f9c1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

2015-03-11 11:49 GMT-03:00 Nikita Popov <nikita.ppv@gmail.com>:

> 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 stil=
l
>> 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?
>

I'm working right now to add full support to ext tokenizer back. I'm not
very experienced with the PHP implementation so, needless to say, I found
numerous ways to break the tokenizer extension \o/

But a solution is getting closer and might get pushed soon. If some harder
problem I don't have enough information to solve arise I'll try to ask for
some advice or collaboration, though it doesn't seem necessary for now as
we still have some time and it's been a great learning experience :)


>
> Also, is this vote about the new implementation now?
>
>
I'm updating the RFC (rush time here gimme a few minutes) to list both
implementations side by side on the patch section, and explaining that the
second patch supersedes the first one.


> Nikita
>
>
M=C3=A1rcio

--001a11340c688258bd051106f9c1--