Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111986 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 5981 invoked from network); 2 Oct 2020 17:29:15 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 2 Oct 2020 17:29:15 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 67A1D180087 for ; Fri, 2 Oct 2020 09:41:42 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-io1-f48.google.com (mail-io1-f48.google.com [209.85.166.48]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 2 Oct 2020 09:41:41 -0700 (PDT) Received: by mail-io1-f48.google.com with SMTP id u19so2227012ion.3 for ; Fri, 02 Oct 2020 09:41:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=83O87CI9q+1ORzXBfEmcu3R6Ll5QaXAG20Q2Dqxxcjg=; b=rmePEXJAFM7z+Gm9yKwKDSm5YE/xmTosFZCdmDLmra2tFjW2uerrqGq4QN+LkDNP/V m0UHBx5lyNhAwAfOTt1yWsU/ZTB0z/EUKm6pYD2DUplnZ0rX+hXZ8a3r0nkMhTGwSO7s 8UmYtj/ydQ46EzbEu8WN+sp1AerXVqkb6B2wduO44LEaaRHhNm9z87hhEk27Zr3a5GoF 1O1zCfMh5Ull+aSdpGix/kSuSuQAIZfEYA1WH7NfR4kNeO0hrU2tIizRxsprZkhpuFsP E6fV9xgIaMn0qrb6ibqMsrC+NXsaJD19xfQEzlYTxVtO6j4/JflDzhAEJnUX8IjSXneY FhUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=83O87CI9q+1ORzXBfEmcu3R6Ll5QaXAG20Q2Dqxxcjg=; b=HeWNjg6pOVIUB2KIp54O28UQUCGmiG4Lcn651pvFS19iXlvHwhxpegFcVvHSFnvK8j U6K62BcSgBbpbgyw9tdtbDlkNM8DydJnLA3qkRIDQSI8w4Cnp7Sif2HHo2Spianhpmjm BQ876FJIrAwj3ZUUzqUuM9mOxsoo487Uj6gfWTxMn44iXtNd9Dv94eau/XuVmlRoN9YG 2uWebZ/Hk3kKFOVxR53iV8Sq0QWU7FUTT2t26XJhp1nCSP332COxRPaFioCcvM7pq1xq OXGm8kJgoNZK7B87DgqUobTWup8fa5cMCk+oR5V8kzx/lyJ4Tum0J5Clxn+uVpxBZeoS a+rg== X-Gm-Message-State: AOAM531bIyZ4zL5ugI59L8HK1yIbiy6+IJ+R/uHu0jPKQbbrH0ibyvP8 XN5iA9SusJoHr1ERwdIDPrceJR8jfX/WfWppWwLG045a4s0= X-Google-Smtp-Source: ABdhPJzsIJ3ezoYvPvpXHtUN+YRoEUi4+QUTG0X4O0Ztvsg1kaaJ5iFtlWLEUK4l2OcSJSwOnqui3m62qmHRPCYYHtQ= X-Received: by 2002:a02:ccca:: with SMTP id k10mr3104827jaq.111.1601656896502; Fri, 02 Oct 2020 09:41:36 -0700 (PDT) MIME-Version: 1.0 References: <940131FA-19B3-406C-8982-0AD276FD1879@gmail.com> In-Reply-To: Date: Fri, 2 Oct 2020 17:41:25 +0100 Message-ID: To: "internals@lists.php.net" Content-Type: multipart/alternative; boundary="0000000000005e432b05b0b2ce92" Subject: Re: [PHP-DEV] RFC: execution opcode file without php source code file From: rowan.collins@gmail.com (Rowan Tommins) --0000000000005e432b05b0b2ce92 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2 Oct 2020 at 10:43, =E2=82=AC=E2=80=93 =E2=80=9Dk=E2=80=9Dk wrote: > For example, Java,.NET, etc., I mean that opcode compiled files can be > bound to fixed versions without considering the compatibility of differen= t > 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, --=20 Rowan Tommins [IMSoP] --0000000000005e432b05b0b2ce92--