Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120653 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 61363 invoked from network); 21 Jun 2023 11:58:10 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 21 Jun 2023 11:58:10 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7023318053F for ; Wed, 21 Jun 2023 04:58:10 -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, 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-wm1-f50.google.com (mail-wm1-f50.google.com [209.85.128.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 21 Jun 2023 04:58:09 -0700 (PDT) Received: by mail-wm1-f50.google.com with SMTP id 5b1f17b1804b1-3f90a7325f6so46704775e9.3 for ; Wed, 21 Jun 2023 04:58:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687348687; x=1689940687; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=TTfceEOwfcxGN+NG/7lRwE+fuPGKbYkoBZYgkT+qYtI=; b=LPp1kWo9iPsjw+5ybWTQg4g4fNnBobyjbEuacsKtrCIjWosxOjh0LvSzWa1H0YM26U 422Rn540U/95Rr0VM+xpRT9MV9In5dlUeZCBWhBEGcR/jm1Fylr6ovaXceFq8jC0zVpp n6X4n5rStGfVNtATocajBIKyk3RuylpQx+RfLv5pTaonbMAq84b6i/r3EYixcNPv7lHu aEOXdnjQcP9f1KE68pUq5BL9h0Lwnejin0wj9AmzosAgahAT+07T4DvQ0ig+5Odz0JiJ naqqVHMNirJPsfB3vt56QhJOFO+cDwWdxskJHB1QC0t1OZQr4c4DRcyiWVyC8B2qCb1q T1NQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687348687; x=1689940687; h=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=TTfceEOwfcxGN+NG/7lRwE+fuPGKbYkoBZYgkT+qYtI=; b=SZzYJ8KpTJ4dQ7ek4nmUuUhV9Vrw07FguorllWodXOj35TGlIxeOPxBr/4Fvdca50S 06FcInHkKTAQVSSu/2cOrYEqi1Oa+EP4HwaFkZDk66xbQPb3rWC6q7/7yG4vHi4ujr/z Cg9VFFecwsEPW4FDEH24BctEFMR28xIHkklF0zLYAc3S48h00b6x9AIzhl/efCyv/Wtc djrhywImZcUEKbZ9m47eHJghy/FwpvlncIS2lnKbl2ccZiUgAPZ9LPQzOMXOl0Kovhwq ylF9GTGw52vFfP2ZdPhJW81aGSNfrXV+2eOeKeyuqOTubBxJJz4nbTezYhdbpQZVO6jY gXOw== X-Gm-Message-State: AC+VfDzcITFca3eb6XiYLMFomQoXgWSl4kgMuJGp7ToLblgoCgVLTlqm xgxp9ynYJOTYzsq6rydyO5N411DgK8XcgfOh0CnGtalt X-Google-Smtp-Source: ACHHUZ5/c+tdg5g4UKIJOUXXuW2gOVPCoJ4BCfSYv0U3jsvp+43mG1pk722PqkKwvR9g8OPfZsyZw2tPjN4NPF5x9c0= X-Received: by 2002:adf:e848:0:b0:311:15ae:2cd2 with SMTP id d8-20020adfe848000000b0031115ae2cd2mr14080239wrn.15.1687348687309; Wed, 21 Jun 2023 04:58:07 -0700 (PDT) MIME-Version: 1.0 References: <108411AD-DBC4-4436-8190-7569B7A0805F@gmail.com> In-Reply-To: Date: Wed, 21 Jun 2023 12:57:55 +0100 Message-ID: To: internals@lists.php.net Content-Type: multipart/alternative; boundary="0000000000001e920505fea27b52" Subject: Re: Fwd: [PHP-DEV] [RFC] [Discussion] Deprecate functions with overloaded signatures From: rowan.collins@gmail.com (Rowan Tommins) --0000000000001e920505fea27b52 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 21 Jun 2023 at 09:43, M=C3=A1t=C3=A9 Kocsis wrote: > The reason why I think it's a good approach to have an intermediate state > is to give > these people the possibility to defer the actual migration until the > very end. > Isn't that exactly what a deprecation period is for? If we want to give people longer, just leave the functionality deprecated for longer before removing it. If we want to phase that in gradually, start with a documentation-only deprecation, and add the deprecation notice later= . If the plan is to keep the current function name, we can't get any of the (very small) benefits of removing the extra signature until the final removal anyway. Regards, --=20 Rowan Tommins [IMSoP] --0000000000001e920505fea27b52--