Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98417 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15232 invoked from network); 7 Mar 2017 06:04:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Mar 2017 06:04:14 -0000 Authentication-Results: pb1.pair.com header.from=sebastian@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=sebastian@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 188.94.27.5 as permitted sender) X-PHP-List-Original-Sender: sebastian@php.net X-Host-Fingerprint: 188.94.27.5 scarlet.netpirates.net Received: from [188.94.27.5] ([188.94.27.5:52924] helo=scarlet.netpirates.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/E0-27071-C5D4EB85 for ; Tue, 07 Mar 2017 01:04:13 -0500 Received: (qmail 25814 invoked by uid 89); 7 Mar 2017 06:05:12 -0000 Received: by simscan 1.4.0 ppid: 25806, pid: 25809, t: 0.0431s scanners: attach: 1.4.0 clamav: 0.99.1/m:/d:20700 Received: from unknown (HELO ?192.168.178.52?) (php@sebastian-bergmann.de@87.156.217.236) by scarlet.netpirates.net with ESMTPA; 7 Mar 2017 06:05:12 -0000 To: internals@lists.php.net References: <0e19e041-4834-c24a-4239-036ab38fbda1@php.net> Message-ID: <314dd971-3a1f-4727-9074-ac0b4089ec97@php.net> Date: Tue, 7 Mar 2017 07:04:12 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] generating code from AST From: sebastian@php.net (Sebastian Bergmann) Am 07.03.2017 um 07:01 schrieb David Walker: > When/if there are changes to AST, having a tool like these in core would require them to be updated at the same time. Exactly. > Would this concept also want to extend to a VLD-esque extension as well for > the same reasons? I'd be receptive for abilities to expose the core > internal ast/ops to userland more easily as a core extension Having a bytecode disassembler in core would also be nice, yes.