Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84456 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19813 invoked from network); 9 Mar 2015 08:44:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Mar 2015 08:44:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@beccati.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=php@beccati.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain beccati.com designates 176.9.114.167 as permitted sender) X-PHP-List-Original-Sender: php@beccati.com X-Host-Fingerprint: 176.9.114.167 spritz.beccati.com Received: from [176.9.114.167] ([176.9.114.167:50204] helo=mail.beccati.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 67/D4-29848-D5D5DF45 for ; Mon, 09 Mar 2015 03:44:14 -0500 Received: (qmail 9474 invoked from network); 9 Mar 2015 08:44:09 -0000 Received: from home.beccati.com (HELO ?192.168.1.202?) (88.149.176.119) by mail.beccati.com with SMTP; 9 Mar 2015 08:44:09 -0000 Message-ID: <54FD5D51.10604@beccati.com> Date: Mon, 09 Mar 2015 09:44:01 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: marcio3w@gmail.com CC: PHP internals References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV][RFC][VOTING] Context Sensitive Lexer From: php@beccati.com (Matteo Beccati) Hi Marcio, > 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. I like the approach. I'm no lexer expert but the new PR seems much nicer. Moreover, I like the feature itself but previously voted no on the implementation. I've therefore switched my vote to a "yes". -- Matteo Beccati Development & Consulting - http://www.beccati.com/