Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115818
To: PHP internals <internals@lists.php.net>
References: <CAF+90c9_qu=PiTS81J2mesPfJdz7n5nSi3qoLNLjhEGN-aTytA@mail.gmail.com>
 <df1992f6-fef0-8f62-95d3-dcbc4a5b86d1@gmail.com>
 <CAF+90c_o1eRxPdJBrOai0Vnmsc=-MYpaWq0wY9zNuL_Vc5jm8Q@mail.gmail.com>
 <763725c0-870b-e8c4-054b-1ea0481ef877@gmail.com>
 <CAF+90c_1A0jOr2sEafoBWYKw7POXBVnviREdCr=zQQGi+Y_qnA@mail.gmail.com>
Message-ID: <f78ac172-940b-8a25-d4d6-8cbe84d64e8e@gmail.com>
Date: Wed, 25 Aug 2021 15:49:32 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c_1A0jOr2sEafoBWYKw7POXBVnviREdCr=zQQGi+Y_qnA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] Deprecate dynamic properties
From: rowan.collins@gmail.com (Rowan Tommins)

On 25/08/2021 15:00, Nikita Popov wrote:
> I'm not sure it will have a big impact for this use-case though, 
> because using the new name would require polyfilling it, so I'd expect 
> people would stick to the old name in the foreseeable future...


Not necessarily - it depends what versions you need to support, and what 
your migration strategy is.

Since it's just a deprecation notice initially, you could support 8.1 
and 8.2 on the same code base with no changes at all - that's what 
deprecation notices are for, to give a lead time before changes are 
mandatory.

Once the code base no longer needed to support 8.1, "extends 
DynamicObject" could be added. For many code bases, that will be long 
before the feature is actually removed - for a private project, maybe as 
soon as it's on 8.2 in production.

Regards,

-- 
Rowan Tommins
[IMSoP]