Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62818 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43484 invoked from network); 4 Sep 2012 20:48:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Sep 2012 20:48:56 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 64.22.89.134 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 64.22.89.134 oxmail.registrar-servers.com Received: from [64.22.89.134] ([64.22.89.134:54256] helo=oxmail.registrar-servers.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 06/86-12568-83966405 for ; Tue, 04 Sep 2012 16:48:56 -0400 Received: from [192.168.0.200] (5ad3285b.bb.sky.com [90.211.40.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oxmail.registrar-servers.com (Postfix) with ESMTPSA id A5C53F009D; Tue, 4 Sep 2012 16:48:52 -0400 (EDT) Message-ID: <5046690F.2060505@ajf.me> Date: Tue, 04 Sep 2012 21:48:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Sean Coates CC: Nikita Popov , PHP internals References: <1D74CBCD-463E-419C-90AB-C1BA774381B6@seancoates.com> In-Reply-To: <1D74CBCD-463E-419C-90AB-C1BA774381B6@seancoates.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Moving to an AST-based parsing/compilation process From: ajf@ajf.me (Andrew Faulds) On 04/09/12 21:45, Sean Coates wrote: > 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? Sure. We're changing the route we go down to produce those opcodes, but not the opcodes themselves. > 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? Compatible, I think. Although I don't know if in the process some might be changed, but I would expect no big changes. -- Andrew Faulds http://ajf.me/