Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116402
Message-ID: <0e1ee90b-fdb7-df28-31f6-24b8fc635c3c@gmail.com>
Date: Tue, 16 Nov 2021 09:06:01 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.3.0
Content-Language: en-GB
To: internals@lists.php.net
References: <CAF+90c9_qu=PiTS81J2mesPfJdz7n5nSi3qoLNLjhEGN-aTytA@mail.gmail.com>
 <CAL0xaBGNn8uNLvf7UKdMgcHiNfMbw2nod1EtD9pYwdeQKJxOsg@mail.gmail.com>
In-Reply-To: <CAL0xaBGNn8uNLvf7UKdMgcHiNfMbw2nod1EtD9pYwdeQKJxOsg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Deprecate dynamic properties
From: rowan.collins@gmail.com (Rowan Tommins)

On 15/11/2021 18:27, Arvids Godjuks wrote:
> If a 3rd party package combines fixing major bugs with a release of a
> significant version and including also the new attribute that's available
> only on newer PHP version?


Just to be clear, attributes are designed in such a way that you, and 
third-party packages, can add this attribute *right now*, in your PHP 
7.4 code, with no ill effects. In older versions, it's a comment (as 
long as it's on its own line); and in 8.0 and 8.1 it will be parsed as 
an attribute, but simply do nothing.

You can add the attribute to every single class, and slowly remove it 
when you're confident of each class not needing it; or you can collect 
the E_DEPRECATED messages and add the attribute to every class 
mentioned. Even in PHP 9.0, there will be no subtle behaviour 
differences; the code will either run, or you will get an error in 
exactly the same circumstances as the E_DEPRECATED messages.

Regards,

-- 
Rowan Tommins
[IMSoP]