Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111414 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 16857 invoked from network); 10 Aug 2020 08:38:39 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 Aug 2020 08:38:39 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 26DDE1804AA for ; Mon, 10 Aug 2020 00:37:46 -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-lj1-f181.google.com (mail-lj1-f181.google.com [209.85.208.181]) (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 ; Mon, 10 Aug 2020 00:37:45 -0700 (PDT) Received: by mail-lj1-f181.google.com with SMTP id i10so8489743ljn.2 for ; Mon, 10 Aug 2020 00:37:45 -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 :cc; bh=IdR8WvQDNIKBvqUBjYwsZygCwO6JAuYS42IhyDg3hZM=; b=VLC9aCmWCPS06zmPz+ksymMA52ABbZ76QmnfbADzC73pKA2Y0Uy7nuEX70l8gj7bgJ fZjcKIv+yeVW1mg5JjF2VTDiQxSgBljZZl4HbQoYIVjfZuehP0yW+afksJLPX79AtKJ4 liWwcs1da2+qUtvwmf4PC9bXHxN3ztsZp2IAtZdcYZslgocoIm/2gidk3f5sOYkCuUyp wbFb94270ptSc290BQZwJjA1MK2FZBomnSlMev//gm76dqT+sMi/h5tJzd8/3/lz6Lwl knUwYJ4cbDT7dhrobGee+5G3yzyFCe+lJ8Ld+9uumTWLz6a10kQCoav9bDP28mNofhtB hxmA== 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:cc; bh=IdR8WvQDNIKBvqUBjYwsZygCwO6JAuYS42IhyDg3hZM=; b=lpJYxFvBTrI2Ud2+WWkNuQBKHYD5X0R1SXo6rsc+rXZaKjPHN2adCTT9v6Qkn9++2B XAGdmUebUGg8uDcoGsIKR0QPcdu7111RH3BgOj2Bs9vx3tpBfoECtzuMpjA1dzRdC7bi gYV53Bj/RYCc8ohn4+ziaoLUPkvecfw7OmsuoSA9L7hbPs+9adJBvAgV7StSIiO8OFC1 L9uSUuSkEPR5HbXsSGmWAZGddI6QfJGp7oA950Qmd3IOTtt6IcAcsw5Mr0oVrLKG0+sp J6KKWtJn3ZljLhAIZib636ivF2STZWqc5WIrTB9wKm9YkDg3rXQyOCRcqDr8uLNvEWjM t5sA== X-Gm-Message-State: AOAM532MvNeV2VibM8CmRAY9GhmUBto8c+9kj7g6vkcvp6SSjKHzaRe7 l8ATpINySw0jUNJvM4CXpsnfCxBrMgXdN4ITGTK81Ua9HMM= X-Google-Smtp-Source: ABdhPJy/WVXaZEFbK0OIwEPa9MjeWkjwAwZ6xsiIYOttsaeMkOhtuRNqncQkmNcQGVTcFQPhAx6RVhttmxEtM53ZFEk= X-Received: by 2002:a2e:3202:: with SMTP id y2mr12534000ljy.30.1597045061520; Mon, 10 Aug 2020 00:37:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 10 Aug 2020 09:37:25 +0200 Message-ID: To: Philip Hofstetter Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000095125605ac810716" Subject: Re: [PHP-DEV] ZEND_ENGINE_4 define? From: nikita.ppv@gmail.com (Nikita Popov) --00000000000095125605ac810716 Content-Type: text/plain; charset="UTF-8" On Mon, Aug 10, 2020 at 7:57 AM Philip Hofstetter < phofstetter@sensational.ch> wrote: > Hello, > > I'm currently looking into porting some extensions (both internal and > public) to PHP 8 while still keeping support for PHP 7 (for the public > ones) and PHP 5.6 (don't ask :-(). > > In many cases, I've been using the ZEND_ENGINE_3 define to handle the > PHP 5/7 difference. > > Now, the Zend Engine version seems to have been increased to 4 (which > feels warranted given the zval* to zend_object* changes for object > handlers), but ZEND_ENGINE_3 is still defined whereas there's no > ZEND_ENGINE_4. > > Is this something that might change or should I just use > PHP_VERSION_ID comparisons to deal with the zval* to zend_object* > changes? > > Philip > I would recommend using PHP_VERSION_ID. I have no idea why we have the ZEND_ENGINE_3 constant, but it seems like a pretty bad idea. Now that we are at ZE 4, should we drop that constant -- and break all the code using it? Chances are that code guarded by ZEND_ENGINE_3 is also needed on all versions of ZE going forward, not just ZE 3 in particular. I think we should just leave teh ZEND_ENGINE_3 define around, but make sure not to introduce a new one of that kind. Regards, Nikita --00000000000095125605ac810716--