Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120308 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 73393 invoked from network); 16 May 2023 11:06:09 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 May 2023 11:06:09 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id DBB3718004D for ; Tue, 16 May 2023 04:06:08 -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-pg1-f171.google.com (mail-pg1-f171.google.com [209.85.215.171]) (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 ; Tue, 16 May 2023 04:06:08 -0700 (PDT) Received: by mail-pg1-f171.google.com with SMTP id 41be03b00d2f7-52cb78647ecso8835234a12.1 for ; Tue, 16 May 2023 04:06:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684235167; x=1686827167; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ILRZViL2LupEgAqqrdz++z/lqgWHI69xJkiniz5e8jY=; b=OuJR/XdiIOzyuMDZuVWKheXy8tP5SDaxIDRDORDiuUHweg4AkOlo0CNuvZk6l1oMDc RQly0p2P8nCmY0iZ7smHgcmlY9AsC5Qc2xU/QKDVMYrCXSsM0Fw+iwxnzG/qENCd2BIZ l49HTnyxXtYtwS8LdEXeSzBUfnzl1ojcdxXpUz8CvzHk0A4aeKmzElC5rW/JHrhJLLRv HJzlW28wZ1j8WDa51VtTWfkOqMeZf5+7bXw/dhQUQX37AvWVFqgYHKfJc8WTRn18n3Rw +nmPuk8SoZHm3RnLhrR0sM/AD3/EpQyhaj0U+QM0p5rvquiDGPsMbdNhmJYZX0YGObEh FpCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684235167; x=1686827167; 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=ILRZViL2LupEgAqqrdz++z/lqgWHI69xJkiniz5e8jY=; b=L28CotuQeHj/5/QucNAYTyQmkaXt03ycbuC28X1hg89BTEEJDMrI9XZ1IME0CNaZsr 50V9Hxc7pXkQFLX49rvCy8wIgIWMIVBNuQ5xO+u3c8QWFFPymGX+zA993TT42RmjHtHu nmN4OFbPDrROZIfn8yU0C5q3i3ZbkWgYG5HA3ju63tN+kp4DolTUhkxxVawpoOdov+G+ jkDfRG3gloc2zAVlzERG7cvSPa3iAPROXeG+DZ4g9ps6ZGqGeXj6juB1EZdJ6ci95dAn IfcR7qJdJ++7BsKOS7yP0U00zRgMAht0Pag8pQ9uKQU7BwGkTdiik2W/dfv8TPGgDflg 9dog== X-Gm-Message-State: AC+VfDwZRVe4KMJdhy7VujYstlViQe1TAH/4OAZsn/5dZfh45bHpmdVA MaNUb3b9rl+XixU+UP90xil0WtnucQA/Z0rempR+FjiLu6o= X-Google-Smtp-Source: ACHHUZ5X42ZR/NdEIOAhkTAHoCulVft9JI7Toxq80ldH0qAxeVFw0+W4TWZrn8Yw4vopg2K8rNGvJPc7Qqljzvulf7I= X-Received: by 2002:a17:902:8491:b0:1ad:eb62:f61c with SMTP id c17-20020a170902849100b001adeb62f61cmr13742945plo.11.1684235167449; Tue, 16 May 2023 04:06:07 -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> <731143A6-D1A2-47E1-B878-8F4C5906139C@gmail.com> In-Reply-To: Date: Tue, 16 May 2023 12:05:55 +0100 Message-ID: To: Larry Garfield Cc: php internals Content-Type: multipart/alternative; boundary="000000000000dfc57205fbcd8e98" Subject: Re: [PHP-DEV] [RFC] [Discussion] Deprecate functions with overloaded signatures From: george.banyard@gmail.com ("G. P. B.") --000000000000dfc57205fbcd8e98 Content-Type: text/plain; charset="UTF-8" On Mon, 15 May 2023 at 19:39, Larry Garfield wrote: > Tangent: If I were to put together an RFC that set out such a 5 year cycle > expectation with reasonable guidelines around when things could be > deprecated, would anyone actually support it? > No, as this doesn't solve the problem. Best regards, George P. Banyard --000000000000dfc57205fbcd8e98--