Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123211
Message-ID: <9CE563A9-649F-43B4-AAA3-238BF8A7B311@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_669467DC-BD1D-48EA-9510-4B4C486BD08A"
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.8\))
Subject: Re: [PHP-DEV] [RFC] [Discussion] #[\Deprecated] attribute again v1.3
Date: Thu, 25 Apr 2024 17:01:35 -0400
In-Reply-To: <c0ebb909-349b-4c86-971c-fe9b8a7b93d6@rwec.co.uk>
Cc: internals@lists.php.net
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
References: <5814C522-CD23-4194-A344-1B57CC0A2511@rwec.co.uk>
 <A5567713-62C7-440E-88DB-AF3D8BA2E750@koalephant.com>
 <c0ebb909-349b-4c86-971c-fe9b8a7b93d6@rwec.co.uk>
From: mike@newclarity.net (Mike Schinkel)


--Apple-Mail=_669467DC-BD1D-48EA-9510-4B4C486BD08A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On Apr 25, 2024, at 11:28 AM, Rowan Tommins [IMSoP] =
<imsop.php@rwec.co.uk> wrote:
> If the project has no clear deprecation policy, the information is =
useless anyway.

Not true.

Having standardized notation for deprecation would allow tooling to =
analyze a codebase and determine if it contains deprecated code that =
needs to be remediated without having to run the code with full =
coverage. =20

Actually, `since:` doesn't go far enough because it doesn't indicate if =
the deprecation throws warnings, throws errors, or just no longer works. =
 The latter two would be especially helpful when deciding if code =
modifications are necessary before upgrading to a new version of PHP.

-Mike=

--Apple-Mail=_669467DC-BD1D-48EA-9510-4B4C486BD08A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Apr 25, 2024, at 11:28 AM, Rowan Tommins [IMSoP] &lt;<a =
href=3D"mailto:imsop.php@rwec.co.uk" =
class=3D"">imsop.php@rwec.co.uk</a>&gt; wrote:</div><div class=3D""><div =
class=3D"">If the project has no clear deprecation policy, the =
information is useless anyway.<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div></div><blockquote style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;" class=3D""><div>Not true.</div><div><br =
class=3D""></div><div>Having standardized notation for deprecation would =
allow tooling to analyze a codebase and determine if it contains =
deprecated code that needs to be remediated without having to run the =
code with full coverage. &nbsp;</div><div><br =
class=3D""></div><div>Actually, `since:` doesn't go far enough because =
it doesn't indicate if the deprecation throws warnings, throws errors, =
or just no longer works. &nbsp;The latter two would be especially =
helpful when deciding if code modifications are necessary before =
upgrading to a new version of PHP.</div></blockquote><div><div><br =
class=3D""></div><div>-Mike</div></div></body></html>=

--Apple-Mail=_669467DC-BD1D-48EA-9510-4B4C486BD08A--