Re: [RFC][Discussion] Parser extension API
| From: | Leigh | Date: | Tue, 17 Feb 2015 12:48:42 +0000 |
| Subject: | Re: [RFC][Discussion] Parser extension API | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-82953@lists.php.net to get a copy of this message | ||
On 17 February 2015 at 12:22, Alexander Lisachenko
<lisachenko.it@gmail.com> wrote:
> 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.
So: Internal Parse AST -> Extension Parse AST -> Generate OpCodes -> OpCache?
So if the parser extension does anything dynamic, then OpCache will
have the wrong version cached.