On Fri, 2 Oct 2020 at 10:43, €– ”k”k <chopins.x...@gmail.com> wrote:
> For example, Java,.NET, etc., I mean that opcode compiled files can be > bound to fixed versions without considering the compatibility of different > versions. > As I said already, this comparison is simply incorrect: both .net and Java have been carefully engineered so that code compiled for one version can be run on later versions. PHP's VM does not even guarantee compatibility from one bugfix to the next, or with and without a particular debugging or extension loaded. > If a different version of opcode is executed, the patch reports an > E_STRICT error. > To be clear, the possible consequences of loading opcodes on the incorrect version would include crashing with a segmentation fault. That's why the existing code, which your patch by-passes, refuses to load the file at all if the "system_id" does not match. An E_STRICT is completely inappropriate for this scenario. Regards, -- Rowan Tommins [IMSoP]
