Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115297
MIME-Version: 1.0
References: <CAF+90c96J7dyq1KsgoPTndM09V=oj46cXm0SxjfkJXiL3TjdHg@mail.gmail.com>
 <CACwt+JfrMa3h2GfG0cxNFmJeg3mPDzf6QWV44zuz+xYBqUsJfg@mail.gmail.com>
 <1dcefcec-a3e4-e773-4950-b11d377ecc7f@gmail.com> <122F660D-DE94-4DFE-A0E9-FEC202E89E3A@newclarity.net>
In-Reply-To: <122F660D-DE94-4DFE-A0E9-FEC202E89E3A@newclarity.net>
Date: Mon, 5 Jul 2021 14:03:26 +0200
Message-ID: <CAC5V6ghg+VK-W=Kn8hLgFmj7xbH7V095CkVq4GqHU35t31Lb4w@mail.gmail.com>
To: Mike Schinkel <mike@newclarity.net>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000004d0aaa05c65f1823"
Subject: Re: [PHP-DEV] [VOTE] Deprecations for PHP 8.1
From: guilliam.xavier@gmail.com (Guilliam Xavier)

--0000000000004d0aaa05c65f1823
Content-Type: text/plain; charset="UTF-8"

On Mon, Jul 5, 2021 at 1:39 PM Mike Schinkel <mike@newclarity.net> wrote:

> > On Jul 5, 2021, at 7:14 AM, Rowan Tommins <rowan.collins@gmail.com>
> wrote:
> >
> > On 05/07/2021 11:46, Patrick ALLAERT wrote:
> >> Did we ever deprecated something without the immediate intention of
> >> removing it?
> >
> >
> > 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.
>
> 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.
>
> -Mike
> [1] https://whatis.techtarget.com/definition/deprecated
> [2] https://stackoverflow.com/questions/8111774/deprecated-meaning
>

Hi Mike,

Your links speak *in general*. However this is *specifically for PHP*:
https://www.php.net/manual/en/errorfunc.constants.php#errorfunc.constants.errorlevels.e-deprecated-error
(*emphasis* mine)

    E_DEPRECATED: Run-time notices. Enable this to receive warnings about
code that *will not work in future versions*.

As for "significant BC breakage", isn't that what major versions are for?
(and with the current release plan, 9.0 would be for end 2025, i.e. 4 years
after 8.1)

Regards,

-- 
Guilliam Xavier

--0000000000004d0aaa05c65f1823--