回复: [PHP-DEV] [rfc:direct-execution-opcod e] Whether need __FILE__ the value of the fil e to replace the compiled opcode file path
| From: | kk | Date: | Thu, 10 Dec 2020 14:40:01 +0000 |
| Subject: | 回复: [PHP-DEV] [rfc:direct-execution-opcod e] Whether need __FILE__ the value of the fil e to replace the compiled opcode file path | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-112484@lists.php.net to get a copy of this message | ||
Hi, Aleksander Machniak:
which part is more difficult to read? Can you tell me?
________________________________
发件人: Aleksander Machniak <alec@alec.pl>
发送时间: 2020年12月10日 20:53
收件人: internals@lists.php.net <internals@lists.php.net>
主题: Re: [PHP-DEV] [rfc:direct-execution-opcode] Whether need __FILE__ the value of the file to
replace the compiled opcode file path
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 idea.
But this need to be redacted, because in the current form it's really
hard to read.
--
Aleksander Machniak
Kolab Groupware Developer [https://kolab.org]
Roundcube Webmail Developer [https://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php