Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76296
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
Sender: mike.php.net@gmail.com
In-Reply-To: <CAF+90c-JHQ4MNLEDP6pZgw6YY37j2dzUK3k26cMWdpbXa1jRGA@mail.gmail.com>
References: <CAF+90c-JHQ4MNLEDP6pZgw6YY37j2dzUK3k26cMWdpbXa1jRGA@mail.gmail.com>
Date: Thu, 31 Jul 2014 20:27:05 +0200
Message-ID: <CALJZF3gQf-OxVBuecgb-8rX5XWkQkYXsswNRJ4h3jbW4soEFHw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e014939fc76fed004ff816b94
Subject: Re: [PHP-DEV] [RFC] Introduce Abstract Syntax Tree
From: mike@php.net (Michael Wallner)

--089e014939fc76fed004ff816b94
Content-Type: text/plain; charset=UTF-8

On 31 July 2014 20:11, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals!
>
> I've created a draft RFC and implementation for the introduction of an
> Abstract Syntax Tree (AST) as an intermediate structure in our compilation
> process:
>
>      https://wiki.php.net/rfc/abstract_syntax_tree
>
> The RFC outlines why an AST is beneficial, how it impacts performance and
> memory usage of the compile process and what changes to syntax or behavior
> it introduces.
>
> Furthermore the RFC contains an outline of how the current implementation
> works and what APIs it provides. This section is just an overview and I
> hope to extend it in the future.
>

Sounds great! BTW, wasn't there a related AST GSOC project once?


-- 
Regards,
Mike

--089e014939fc76fed004ff816b94--