Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112602
MIME-Version: 1.0
References: <CAEPJdu=kopidV44A01Sjv_eLq_fkLsjVuzqXx+j9b9gCahn2Vg@mail.gmail.com>
 <CAOWwgpmwdxnwb+NcHcd59ySwbKKB_1C1nYtPeGkmPXa8F3GXPg@mail.gmail.com>
In-Reply-To: <CAOWwgpmwdxnwb+NcHcd59ySwbKKB_1C1nYtPeGkmPXa8F3GXPg@mail.gmail.com>
Date: Tue, 22 Dec 2020 12:54:53 -0600
Message-ID: <CAESVnVpjyhCH1K5sOHzp8qoa7hUAhRqpfN90JS3CooyFpEOZ2Q@mail.gmail.com>
To: Nicolas Grekas <nicolas.grekas+php@gmail.com>
Cc: Benjamin Eberlei <kontakt@beberlei.de>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d1deb605b7121c58"
Subject: Re: [PHP-DEV] #[Deprecated] Attribute
From: pollita@php.net (Sara Golemon)

--000000000000d1deb605b7121c58
Content-Type: text/plain; charset="UTF-8"

On Tue, Dec 22, 2020 at 12:35 PM Nicolas Grekas <
nicolas.grekas+php@gmail.com> wrote:

> It would be great to allow adding this attribute on classes. What about
> allowing it right now and not bind it to any runtime side-effect? That
> would allow static analyzers to do their job. Same for consts and
> properties by the way.
>
> Also, it would be very useful to add named parameters to the attribute,
> namely: "package" (the name of the package that declares the deprecation)
> and "version" (the version of that package that introduced the
> deprecation), next to the message.
>
> This is critical info when building reports of deprecations.
>
>
You could do that now with a polyfill from userspace.  If the annotation
need not have an effect, then it's just any other userspace implementation.

-Sara

--000000000000d1deb605b7121c58--