Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62870
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: internals@lists.php.net
In-Reply-To: <50486309.1090601@php.net>
References:
	 <CAF+90c-+Hgcv5B4+eGDS+jEj6oNoyefBWO-M=kvThaVdckz62g@mail.gmail.com>
	 <504836A3.20904@zend.com>  <50486309.1090601@php.net>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 06 Sep 2012 17:10:26 +0200
Message-ID: <1346944226.3695.13.camel@guyrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Moving to an AST-based parsing/compilation process
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Thu, 2012-09-06 at 09:47 +0100, Sebastian Bergmann wrote:
> On 09/06/2012 06:37 AM, Dmitry Stogov wrote:
> > The only real advantage could be an ability to expose AST to PHP scripts,
> > but only few people may need it.
> 
>   Everyone working on static analysis tools for PHP code needs access to
>   the (canonical) AST. While the number of people behind this "everyone"
>   will be small (hopefully it will grow) but the tools they create based
>   based on the AST will be valuable for every PHP developer.

As soon as those tools should be version independent they need their own
parser anyhow.

Aside from that: I don't see the reason for this discussion now. People
can go and implement until this is done it's hard to argue about
performance etc. as that can hardly be predicted. If people have a need
for this they are free to go. If people don't have a need for this they
won't. (A more relevant question might be "Who wants to invest time on
this", certainly can be a fun project ...)

johannes