Hi, On 1 October 2020 10:36:20 BST, "肖 鑫鑫" <chopins.x...@live.com> wrote: >I commit a new request path, the request is about execution opcode file >without php source code file >this RFC provides similar to class file of java and pyo file of python. >patch is: https://github.com/php/php-src/pull/6146
I'm sure someone who knows the internals better can clarify, but my understanding is that PHP OpCodes don't currently have any stability guarantee, so you can't rely on a binary taken from one version will run on another, even within a release. In order to be useful, this will therefore need two things: - a header in the file identifying the engine version it was compiled for, with an error raised on any mismatch - a policy of how to manage that version number, and how users can know which versions their binary files will work on There's probably a limit to how stable we can (or want to) make the VM, so these files will never be as portable as a Java class file or .Net assembly. Regards, -- Rowan Tommins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
