Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115295 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 47876 invoked from network); 5 Jul 2021 11:17:54 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Jul 2021 11:17:54 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 06A821804D0 for ; Mon, 5 Jul 2021 04:39:22 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-qk1-f170.google.com (mail-qk1-f170.google.com [209.85.222.170]) (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, 5 Jul 2021 04:39:21 -0700 (PDT) Received: by mail-qk1-f170.google.com with SMTP id t19so2039953qkg.7 for ; Mon, 05 Jul 2021 04:39:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HmU6dfRv8PHA2g++pwJdeYGnIx6K5aqsHzhQMpSvriw=; b=R5P7+rnXZnfD4RRKIp0RK62YZYUs7b2J6XSEig6C+6+qw4W9y5SOD54FBom+UYzFl9 1byaFZFDuQKc1kngaKL9xmttKTCgoXymLEy/+T/1fh3EZ20UJeUp2Gn1mw4A1STovZcI z2Tei+S/+628C/sTohieDfmwRc3FKnGhBM2+czC6puPEvTsKfh8yrQJlDTJLPX06S0RG nZjiiOs4p7Ai3iKRgqJtzDVzr5RRsGpRIUa4k2Mq2iHhOjaktjITJiOnX4hQydJVviO6 0umnb0LUxFVI5b8SxkEdCmvQsmeoZXdhrRnFXjoTCX7DOy9vJtB/f3tcVy7LKGzQ/FFb yEcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HmU6dfRv8PHA2g++pwJdeYGnIx6K5aqsHzhQMpSvriw=; b=OS9j102FUdC6ivzEBPGmvZjDYn9tI16eRpx7pkW1z+ph79dofptyvwAzx8GABQjYgi pp3skk9wtG36UcpBMqxjkSYKZYGL2SRy0TYPyxkNuhZ6yyn4Hzxau92j0Rkp76Hck2RZ Sjne1Xn/zUADwC45uB8tp/XWf9wzg5SFD5BR2dwNx20YC+6lCKfSzZn1BVuPuXPMFGq4 byUiN8Q3xFeK1F8PI4RkA0uiTKVZk02BauQ2OTuu7iYLERwI1uliatsMv8rOaXrNJ0bs s31GJxZSrhd2TeQnLQLfYQIoybXkTgvFXK+74FZFu70uJ8HuMsgRRFSqUsWDwBYBgNL4 q08w== X-Gm-Message-State: AOAM53151BjaUWNA87HVRDFcsREEYKA6XPKSqJQWc7pvGoOknMNJQ5F+ IyIw03R89X4Zl4hBoag+cgR+wg== X-Google-Smtp-Source: ABdhPJwK3GvdqIcBssq0uMFmnBYc8Nbax82BpGWW9y2VRJ9fKARs21rxy7eWJMmWsvJwrcSffYy1SQ== X-Received: by 2002:a05:620a:31a6:: with SMTP id bi38mr11259328qkb.140.1625485158281; Mon, 05 Jul 2021 04:39:18 -0700 (PDT) Received: from [192.168.1.10] (c-24-98-254-8.hsd1.ga.comcast.net. [24.98.254.8]) by smtp.gmail.com with ESMTPSA id u4sm4285664qtw.86.2021.07.05.04.39.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Jul 2021 04:39:17 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) In-Reply-To: <1dcefcec-a3e4-e773-4950-b11d377ecc7f@gmail.com> Date: Mon, 5 Jul 2021 07:39:15 -0400 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: <122F660D-DE94-4DFE-A0E9-FEC202E89E3A@newclarity.net> References: <1dcefcec-a3e4-e773-4950-b11d377ecc7f@gmail.com> To: Rowan Tommins X-Mailer: Apple Mail (2.3608.120.23.2.7) Subject: Re: [PHP-DEV] [VOTE] Deprecations for PHP 8.1 From: mike@newclarity.net (Mike Schinkel) > On Jul 5, 2021, at 7:14 AM, Rowan Tommins = wrote: >=20 > On 05/07/2021 11:46, Patrick ALLAERT wrote: >> Did we ever deprecated something without the immediate intention of >> removing it? >=20 >=20 > What would that even mean? It would mean that although the functions are available and allowed, = they are not recommended[1]. > Surely a deprecation, by definition, is a notice that something is = going to be removed. I know that you, and others on this list, have chosen to define = deprecation as including removal, but that is actually not the accepted = definition on the web, nor is it in any way a requirement, it is just = your preference. =20 Indirectly from Wikipedia and voted as the top answer on StackOverflow = here[2] (emphasis MINE): "deprecation is a status applied to software features to indicate that = they should be avoided, typically because they have been superseded. = Although deprecated features remain in the software, their use may raise = warning messages recommending alternative practices, and deprecation MAY = indicate that the feature will be removed in the future." So I am arguing for the legitimacy of retaining "deprecated" features if = their removal would cause significant BC breakage, I'm not just trying = to be a pendant. =20 -Mike [1] https://whatis.techtarget.com/definition/deprecated [2] https://stackoverflow.com/questions/8111774/deprecated-meaning