Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115310 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 26331 invoked from network); 6 Jul 2021 08:08:27 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 6 Jul 2021 08:08:27 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 17E8A1804C9 for ; Tue, 6 Jul 2021 01:30: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,NICE_REPLY_A, 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-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 RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 6 Jul 2021 01:30:09 -0700 (PDT) Received: by mail-wm1-f50.google.com with SMTP id j34so12957704wms.5 for ; Tue, 06 Jul 2021 01:30:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=HWhlgfwMZ4p84RtSjd9B/JMlAsR1heaJjmdaMjsh7wg=; b=YE5FQsfCvCg0StiZlwjGheO/52fwuQj5brPBuJO/3xvhU8r6EKIXM4OPQwTYWtA1Wa fszIn2iL8fIAoXCehVs7j7wXwLqhgR49G2bwdgsYZqokg+g24rycQDjHLK3B1NF7feyT PBUYW92K+j0wB8SGr4tcK1vpHKWiFkSRYDen+KHLnti8qIlHRrVdxSXvFB5GWH3WOIyl ZQ9s5G+GhkiQ9gNteDM3u4pwHaFezbtNtWyIg7cFyhJnwul4Yt5DHzBFFD3tb7u/mGMs FJubcHd9pgcHllIuzSIaAAB72zsw0g56LgLplBhpAo3QIzOYELf3ONBfOneirKq7sGIH +i5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=HWhlgfwMZ4p84RtSjd9B/JMlAsR1heaJjmdaMjsh7wg=; b=TX93mNv3xM9U46d27mrizaVEf5X9qjpiMhrCkgCK/66gR0ZGU+RvC5rfHt1W1OGHB1 uN2BIl52OERzBRIKiW5hGQKJaY90GxdK71uUmwn1YPKJW9AbuSeRF63gGl8zBUMFH5mI bMbG3AIHbE5bjBedlQAIcazLI8pQFvImXwrrLWWFv+XvE62uZpD55BDogQJf1luA9ID8 Xd5Qa5m3Y2Ww53ROSpLIlQHL2iakWVEizXgdy8bqp1Rax69clO1AqnVJuVswmWdIpL6F vGHyRqGJAtCeHnVQKTzqzRSHql8rEOCYocrOc4a6+MNhiC40rY2VBA2Y24jKI62BDjaE Ik/Q== X-Gm-Message-State: AOAM533CeT5C3EIZp5QIGSdgE4UYu+yjtHsVyiHZz6x7Q6zhXx5PVp9f YWwhkRVCZ5voEj+WzcGCkpYP3K+SAHw= X-Google-Smtp-Source: ABdhPJzll0IzwVizIgqZnPo3T8TtXDwI8sPxnk74pHJf2uy6hUtxKd3OK67qioBu8EqjIkGHegPZAg== X-Received: by 2002:a1c:2782:: with SMTP id n124mr3505946wmn.114.1625559854209; Tue, 06 Jul 2021 01:24:14 -0700 (PDT) Received: from [192.168.0.22] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.googlemail.com with ESMTPSA id t22sm1149458wmi.22.2021.07.06.01.24.13 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 06 Jul 2021 01:24:13 -0700 (PDT) To: internals@lists.php.net References: <1dcefcec-a3e4-e773-4950-b11d377ecc7f@gmail.com> <122F660D-DE94-4DFE-A0E9-FEC202E89E3A@newclarity.net> <62eb8eff-e671-5b3b-5e25-2a5b38160fcd@gmail.com> Message-ID: <586591d0-8bbc-a42c-f92b-819b8fc6ac20@gmail.com> Date: Tue, 6 Jul 2021 09:24:11 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB Subject: Re: [PHP-DEV] [VOTE] Deprecations for PHP 8.1 From: rowan.collins@gmail.com (Rowan Tommins) Hi Mike, > Instead I replied because your email strongly implied (stated?) that "deprecation required removal" I stand by that interpretation, which while not universal is very widely used, and I think is more useful than a general hint at "bad practice". You spend most of your e-mail seeming to argue against it, and then seem to say that actually you do agree with it after all, and all you're saying is that sometimes the deprecation period should be longer: > I am not advocating that. I am advocating we should consider making it: > > "features that are strongly discouraged will*probably* be removed in the next major version, but in some cases may be retained for one or more major versions." I'm totally OK with that. I do think that there should be a clear *plan* for removing each deprecated feature, though. That plan might be "deprecate in 8.1, and examine prior to 9.0 whether usage has dropped / the alternatives are mature / etc". It might flat out be "deprecate in 8.1, but don't remove until 10.0". Otherwise, the message becomes "this feature is kind of bad, and at some point we might decide to drop it without further notice, but actually we might not, so no hurry to remove it", which I just think isn't that helpful. Regards, -- Rowan Tommins [IMSoP]