Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82951 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 94377 invoked from network); 17 Feb 2015 12:30:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Feb 2015 12:30:04 -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.171 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 209.85.212.171 mail-wi0-f171.google.com Received: from [209.85.212.171] ([209.85.212.171:49694] helo=mail-wi0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/C1-19463-B4433E45 for ; Tue, 17 Feb 2015 07:30:04 -0500 Received: by mail-wi0-f171.google.com with SMTP id hi2so32508590wib.4 for ; Tue, 17 Feb 2015 04:29:59 -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=HZIaaEd7I3qGCJydhKCCWnQFg7p6JWLth4ENTCPa+UQ=; b=fMrClBxNEAgbDaQcID0Hqp1idWSOE1P3egIzOf957JkArGy2KAlxlR1MrWESPXte/J 2IKyazU05xDyOXR/c4moDffSkmTZmdrQSGTE7Bgh7mCHMj5CvR6h0rBaE/K7/SKRuTgU bz0Kgoz5nS0VCMPAyWzN4+lDg1hwWyj09+6d1UxEtoKd44ZZm7hwH+2htmfro9UpnmTP uYSNkwniomq7/2C47WDhttHfIxMD4oCSa8HZFYJJ/unUzwS8AUxBDvt1wnL4/W8b5SfB 7c2lRDoS6MNTlmmaRSimV/IJLUsALHT89XZLX9T3xNSksr/fwY0u2nVLTSjfTCorc1la ot3A== X-Gm-Message-State: ALoCoQkzejJ3clO4+0cTISUXu3bTEi7PBIFG1A8bYKccXWmQ31KzGWO2cwKCKniqDm9tdN6fKFyX MIME-Version: 1.0 X-Received: by 10.180.149.242 with SMTP id ud18mr47082281wib.94.1424176199051; Tue, 17 Feb 2015 04:29:59 -0800 (PST) Received: by 10.194.192.202 with HTTP; Tue, 17 Feb 2015 04:29:58 -0800 (PST) X-Originating-IP: [93.129.120.219] In-Reply-To: References: Date: Tue, 17 Feb 2015 13:29:58 +0100 Message-ID: To: Alexander Lisachenko Cc: PHP internals list Content-Type: multipart/alternative; boundary=001a11c26958713e6f050f47dc39 Subject: Re: [PHP-DEV] [RFC][Discussion] Parser extension API From: kontakt@beberlei.de (Benjamin Eberlei) --001a11c26958713e6f050f47dc39 Content-Type: text/plain; charset=UTF-8 On Tue, Feb 17, 2015 at 1:22 PM, Alexander Lisachenko < lisachenko.it@gmail.com> wrote: > > 2015-02-17 15:09 GMT+03:00 Benjamin Eberlei : > >> The visitor API is the essential part here and you left it out. > > > Yes, I decided not to put Visitor in the RFC (this was added as open > question to the RFC). But this part can be discussed in the case of general > acceptance. > > > 2015-02-17 15:09 GMT+03:00 Benjamin Eberlei : > >> How does this work with Engine Extensions, are they considered for all >> require/include's *after* the registrtion? How does this work with opcache? > > > Yes, parser extensions will be called for all require/include/evals after > registration. This part is transparent for opcache, because opcache just > stores an opcodes for the file. AST is parsed only once for each file, then > hooks can transform the AST and after that compiler will produce a final > opcodes that can be stored for that file in the opcache. So, I expect no > impact on opcache logic. > Well not really, depending on the path towards a require a parser extension is already registered or not. Or you have conditional registration of extensions. So you could load a file with an extension registered, but it still serves the old opcodes for that file. --001a11c26958713e6f050f47dc39--