[VOTE] Direct execution opcode file without php source code file

On Sun, Apr 4, 2021 at 9:11 PM €– ”k”k <chopins.xiao@gmail.com> wrote:

Voted no because, as stated during discussion, this is brittle, provides a false sense of security, and doesn't fix any problem. -Sara

On Sun, Apr 4, 2021 at 8:11 PM €– ”k”k <chopins.xiao@gmail.com> wrote:

For those who want to execute opcodes without needing to have the source available, there are multiple hurdles that need cleared. The largest one I am familiar with (and I'm sure there are many more) is this: many hooks in the engine used by extensions and zend_extensions can cause the "system id" to change. Whenever the system id changes, the opcache must be invalidated and rebuilt, which requires the source to be available. Adding opcode handlers, requesting cache slots, and many, many more extension points all affect this. Some of these things can probably be done differently and not affect the system id, though in some cases at a performance loss. Other things may require a new, successor API that fills an equivalent purpose but without affecting the system id.

Voted no as well. As point out during discussion, we are still not clear about the advantages of this proposal. There are other competitive, if not better, alternatives for the scenarios that the author suggested. Regards, CHU Zhaowei

On 05.04.2021 04:11, €– ”k”k wrote:

I voted No because I can't imagine anyone voting Yes to a RFC as badly written as this one.