Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82948 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88630 invoked from network); 17 Feb 2015 12:09:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Feb 2015 12:09:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain beberlei.de from 209.85.212.182 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 209.85.212.182 mail-wi0-f182.google.com Received: from [209.85.212.182] ([209.85.212.182:65496] helo=mail-wi0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FD/A0-19463-58F23E45 for ; Tue, 17 Feb 2015 07:09:41 -0500 Received: by mail-wi0-f182.google.com with SMTP id l15so31865875wiw.3 for ; Tue, 17 Feb 2015 04:09:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XlH8rgsAjzydJE9A0j7xWDl0r1OouLu/8hdoh4ojQeA=; b=bXdfFcCHfUdMLTriXoopLXhjuetMrkJ70VR4i4y6Lp9x6CFQ/b0eztCPCw8BO+14hG /XUmvjgrvulyMh56VyyMQgeRg6MEXKGsaHVIXUtZNOQkVzUgnystkuvIHKPpiqKUzU4m oMm/cxpnaM5RiNqJVTWeo40K76S8V4/TcKrtOnG6rctEFrhGNpsu1OdXBrGLhQvaoxPm kKU/O3u0Eit4dgIWODdhOumvSJNrU868gxL+Qz4irgV/HdhDxk850TPilK7B4u2MBbEB zKTQF1wnIrBi5A46/3nYxedNY840j61YI4v+4s+hKMMXBYhhePhHLtC1Q6fX7aAE8ivQ HnrQ== X-Gm-Message-State: ALoCoQmI6SJNvAmmIEzIsWtlKCJJotOATc/b8WvR+SiFdjHUGN1TIMsj02eRSgC3I3McglXUVCdR MIME-Version: 1.0 X-Received: by 10.180.206.98 with SMTP id ln2mr45997746wic.94.1424174978326; Tue, 17 Feb 2015 04:09:38 -0800 (PST) Received: by 10.194.192.202 with HTTP; Tue, 17 Feb 2015 04:09:38 -0800 (PST) X-Originating-IP: [93.129.120.219] In-Reply-To: References: Date: Tue, 17 Feb 2015 13:09:38 +0100 Message-ID: To: Alexander Lisachenko Cc: PHP internals list Content-Type: multipart/alternative; boundary=001a11c381ceae76ff050f479347 Subject: Re: [PHP-DEV] [RFC][Discussion] Parser extension API From: kontakt@beberlei.de (Benjamin Eberlei) --001a11c381ceae76ff050f479347 Content-Type: text/plain; charset=UTF-8 On Tue, Feb 17, 2015 at 12:46 PM, Alexander Lisachenko < lisachenko.it@gmail.com> wrote: > Hello, internals! > > I want to introduce a RFC for providing a userland API for accessing an > Abstract Syntax Tree of the source code and to provide userland parser > hooks for source code modification: > https://wiki.php.net/rfc/parser-extension-api 1. The visitor API is the essential part here and you left it out. 2. How does this work with Engine Extensions, are they considered for all require/include's *after* the registrtion? How does this work with opcache? > > > > Thanks! > --001a11c381ceae76ff050f479347--