Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62817
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain seancoates.com from 64.15.79.181 cause and error)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-30--882830225
In-Reply-To: <CAF+90c-+Hgcv5B4+eGDS+jEj6oNoyefBWO-M=kvThaVdckz62g@mail.gmail.com>
Date: Tue, 4 Sep 2012 16:45:57 -0400
Cc: PHP internals <internals@lists.php.net>
Message-ID: <1D74CBCD-463E-419C-90AB-C1BA774381B6@seancoates.com>
References: <CAF+90c-+Hgcv5B4+eGDS+jEj6oNoyefBWO-M=kvThaVdckz62g@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] Moving to an AST-based parsing/compilation process
From: sean@seancoates.com (Sean Coates)

--Apple-Mail-30--882830225
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> Some people asked me what the advantages of using an AST-based
> parsing/compilation process are, so I put together a few quick notes
> in an RFC:
>=20
> https://wiki.php.net/rfc/ast_based_parsing_compilation_process
>=20
> It would be nice to get a few comments from other core devs on this.

Pardon my obviously amateur question, but would you build an AST-based =
compiler/parser to generate the same (minus the ones you intend to =
eliminate) opcodes to run on the VM in the same way as the current =
compiler does?

Would tools like XDebug, APC, Zend PHP encoder (or whatever that's =
called this week), etc. be compatible out of the box, or would changes =
need to be made to them?

Also, here is a potential starting point if you're less allergic to =
OCaml than I am: https://github.com/facebook/pfff

S=

--Apple-Mail-30--882830225--