Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62853 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96700 invoked from network); 6 Sep 2012 08:51:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Sep 2012 08:51:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=sebastian@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=sebastian@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 93.190.64.36 as permitted sender) X-PHP-List-Original-Sender: sebastian@php.net X-Host-Fingerprint: 93.190.64.36 mail-6.de-punkt.de Received: from [93.190.64.36] ([93.190.64.36:57062] helo=mail-6.de-punkt.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3C/B0-27906-31468405 for ; Thu, 06 Sep 2012 04:51:32 -0400 Received: (qmail 3288 invoked by uid 511); 6 Sep 2012 08:51:26 -0000 Received: by simscan 1.3.1 ppid: 3282, pid: 3286, t: 0.0341s scanners: attach: 1.4.0 Received: from unknown (HELO ?10.26.1.180?) (php%sebastian-bergmann.de@195.194.77.144) by 0 with ESMTPA; 6 Sep 2012 08:51:26 -0000 Message-ID: <50486410.4010407@php.net> Date: Thu, 06 Sep 2012 09:51:28 +0100 Reply-To: internals@lists.php.net User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0 MIME-Version: 1.0 To: internals@lists.php.net References: <504836A3.20904@zend.com> <50485647.1060102@hoa-project.net> <50485AA6.4090803@sugarcrm.com> In-Reply-To: <50485AA6.4090803@sugarcrm.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Moving to an AST-based parsing/compilation process From: sebastian@php.net (Sebastian Bergmann) On 09/06/2012 09:11 AM, Stas Malyshev wrote: > As for third-party tools, I do not see why third-party tools need PHP > to change the parser. If PHP's parser is not good enough for those tools, > they can have their own parser. Nikita is doing an amazing job with PHP_Parser, which is such a third-party tool. However, it will always lag behind the canonical parser. And it will (probably) never match 100% the behavior of the canonical parser. This is why, from my perspective of someone who is interested in static analysis and quality assurance, I think that it would be a tremendous boost for the PHP platform if we had a state-of-the-art parser for the reference implementation of our programming language.