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
On Thu, Dec 10, 2020 at 8:40 AM €– ”k”k 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
Hi, Aleksander Machniak:
which part is more difficult to read? Can you tell me?
发件人: Aleksander Machniak
发送时间: 2020年12月10日 20:53
收件人: internals@lists.php.net
主题: Re: [PHP-DEV] [rfc:direct-execution-opcode] Whether need __FILE__ the value
of the file to replace
On 10.12.2020 13:46, €– ”k”k wrote:
> Magic constant __FILE__ and __DIR__ of values is source code path, whether
> need replace to opcdoe file path at compile time
>
> RFC see : https://wiki.php.net/rfc/direct-execution-opcode
That's not my field of expertise, so I can't say much about the
Magic constant __FILE__ and __DIR__ of values is source code path, whether need
replace to opcdoe file path at compile time
RFC see : https://wiki.php.net/rfc/direct-execution-opcode
