Re: 回复: [PHP-DEV] [rfc:direct-executio n-opcode] Whether need __FILE__ the value of the file to rep lace the compiled opcode file path
| From: | Morgan Breden | Date: | Thu, 10 Dec 2020 20:20:04 +0000 |
| Subject: | Re: 回复: [PHP-DEV] [rfc:direct-executio n-opcode] Whether need __FILE__ the value of the file to rep lace the compiled opcode file path | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-112486@lists.php.net to get a copy of this message | ||
I'm not 100% certain but I believe what chopins is proposing is the ability
to require()/include() files generated by opcache, without including the
.php file.
The reference to __FILE__ is I believe a warning to using relative paths,
since the compiled opcode file would be in a different location?
On Thu, Dec 10, 2020 at 10:52 AM Sara Golemon <pollita@php.net> wrote:
> On Thu, Dec 10, 2020 at 8:40 AM €– ”k”k <chopins.xiao@gmail.com> wrote:
>
> > Hi, Aleksander Machniak:
> > which part is more difficult to read? Can you tell me?
> >
> >
> All of it.
>
> I'm sorry, but I have absolutely no idea what you're trying to propose
> here. Something about __FILE__ not being the right value in certain
> circumstances because of something about opcache.
>
> -Sara
>