Re: [RFC] Deprecations for PHP 8.5
| From: | Bob Weinand | Date: | Sun, 06 Jul 2025 17:00:07 +0000 |
| Subject: | Re: [RFC] Deprecations for PHP 8.5 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-127921@lists.php.net to get a copy of this message | ||
Hey Tim,
On 6.7.2025 15:35:16, Tim Düsterhus wrote:
Hi Since this is a recurring thing, I feel compelled to point out terminology: A deprecation in itself is not a breaking change. Let me disagree with this. Yes, a deprecation in *itself* doesn't break running code. However it is both a) an annoyance (you want to get rid of deprecations) and b) a promise that it will be eventually broken.So, it requires a code change, maybe not immediately, but it will. And that's what we're getting at. It will break real code, just not right now. And there's not always a point in breaking real code for the sake of "this might be potentially confusing". (And for the feature in question, I do disagree that it's confusing, but that's not the point of this mail.) Bob