Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120281 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 43618 invoked from network); 15 May 2023 08:54:55 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 May 2023 08:54:55 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id CA9A21804D0 for ; Mon, 15 May 2023 01:54:54 -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_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-pj1-f42.google.com (mail-pj1-f42.google.com [209.85.216.42]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 15 May 2023 01:54:54 -0700 (PDT) Received: by mail-pj1-f42.google.com with SMTP id 98e67ed59e1d1-24e2b2a27ebso11610897a91.3 for ; Mon, 15 May 2023 01:54:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684140893; x=1686732893; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Y2MaedcQBlt7pyfUCVFpVRCSzeC7i9mdW/8WXITMmeg=; b=QBx0Dwo5LQWAHMXGKgUuLo9xV85nzUaKItIUPSSQ7BBUXcH/SAlzy8HirDIHVFc/x2 tM9ymdp/rX+eUPkSq/LV3LkVfWQx8ZpPvF5aHgxxNKxZXG1GIpjffwuShZQIIj/99JFg mGT+bbJJWvPnUY9KThdM5lTo4Ic7ERL3WCj3Q5UMWFXBxiSbv7lqEi2dHUeAyTtCexlR 4P5bVODz5nmO+DXu8+ck/zGshz7Yrfo5jNXcx4N0xDEJ8WAme46PIU2bObEX/ms2D87s jSo31TwtOTIIG9NwoohL5KveDb33wtolIs8R5qTXHVHm+VEzofRksigdtl1qe7zmk0N9 LS1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684140893; x=1686732893; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Y2MaedcQBlt7pyfUCVFpVRCSzeC7i9mdW/8WXITMmeg=; b=Sju3R70aHSSCB2/wYdkuiUC/ofrygt5tYFuOFQ1KhvKLP7cZKN2pHxHUjAN9+a/mOR /3p/fgm6A/QufvYbNj63/CFS6REmOFCHvCxeYztXYZzkLqBHtNfjx37TPKpQlciGGfvA BJ1riM71PP8RWLSntNQVkxpXpiD0Q0G8hgTWh4QuSp3Z0v8NjbR6E9+hUnXnX9/zgVAS oZacNKjYC6qXJCZCBx1rOwoUaBO8f3PGYF5UoU3zVv64g0rLNPU+cUnKrPFaHBjywZzv Znit4AxGZQLirxRsK6MUeqVRPhB0mKzRWUgAL9mA8YfO1OtXNWxtOl2R0kOpisdBuSbT eUlQ== X-Gm-Message-State: AC+VfDznaK4zjsmuVBNDHgkbUj98ou/QKpn2xh6akuFrMSlHdSgLujig emMhWNSHf9zdYJX4Aw4/0v8+M6HbxyoRE40mlqD1M3FpbR7OIA== X-Google-Smtp-Source: ACHHUZ5pWp7Q6qqBCgFe0klpV0oNP37FjL1eQOIr/cyNfJlsDVfhL+mR2JHWPrVJz6efYPttMZXdZSdnQRDfrTpgYl4= X-Received: by 2002:a17:90a:b00a:b0:250:1905:ae7b with SMTP id x10-20020a17090ab00a00b002501905ae7bmr33001736pjq.27.1684140893219; Mon, 15 May 2023 01:54:53 -0700 (PDT) MIME-Version: 1.0 References: <9ab0173f-a6f2-66f6-3ab3-d5f0c44feb05@bastelstu.be> <9F928894-199E-4C46-A590-136BDDE035F7@gmail.com> <68c1b984-1bcd-4dfd-8499-65fe392d7783@app.fastmail.com> In-Reply-To: <68c1b984-1bcd-4dfd-8499-65fe392d7783@app.fastmail.com> Date: Mon, 15 May 2023 09:54:41 +0100 Message-ID: To: Larry Garfield Cc: php internals Content-Type: multipart/alternative; boundary="000000000000b1312b05fbb79b47" Subject: Re: [PHP-DEV] [RFC] [Discussion] Deprecate functions with overloaded signatures From: george.banyard@gmail.com ("G. P. B.") --000000000000b1312b05fbb79b47 Content-Type: text/plain; charset="UTF-8" On Sat, 13 May 2023 at 00:08, Larry Garfield wrote: > That means it's impossible to write code that works from 8.2 to 9.0 > without version checks. The overlap period is only 2 releases (8.3 and > 8.4). That's too short of a window. > Why are we assuming that PHP 9.0 is going to come after PHP 8.4? There has been no decision as to when the new major is going to be released. And as far as I'm concerned, the only good reason to move from 8.x to 9.0 is when we convert streams from resources to objects, which is going to be a large enough BC that those sorts of minor BC breaks should frankly be a non-issue. So could we not speculate on an arbitrary timeline of the new major version being tagged and go on the merit of this proposal in isolation? I don't see much of an issue of, introduce the new functions/methods in PHP 8.3, deprecate them in PHP 8.3+x (for x > 0) and remove in PHP 9.0. Best regards, George P. Banyard --000000000000b1312b05fbb79b47--