Re: [PHP-DEV] [RFC] Deprecations for PHP 8.6

Hey everyone,

after talking to Gina and Tim I would like to ask here if there would be 
any objections against me, under "minor change", removing the "deprecate 
static properties" part from my >Deprecate using "namespace" as a class 
constant or static property name< contribution to the RFC -- hence 
limiting the scope.

Reason: for what my RFC intended deprecating using "namespace" as a 
static class property is not actually required; and using "class" as 
static property name is also legal although it is a reserved keyword. 
Not deprecating "name" in class constants would roughly lead to -50% 
from the impact analysis Juliette did.

---

Cheers
Nick

On 30.06.26 03:39, Nick Sdot wrote:
>
> On 22.06.26 21:13, Gina P. Banyard wrote:
>> Hello internals,
>>
>> It is this time of year again where we proposed a list of 
>> deprecations to add in PHP 8.6:
>>
>> https://wiki.php.net/rfc/deprecations_php_8_6
>>
>> As a reminder, this list has been compiled over the course of the 
>> past year by different people.
>>
>> And as usual, each deprecation will be voted in isolation.
>>
>> We still have a bit of time anyone else to propose additional 
>> deprecations, and if you have write access feel free to add them 
>> directly to the RFC.
>> Please note that with the new RFC policy rules the RFC must be 
>> finalized and in a "frozen" state by the 13th of July at the latest.
>>
>> Some deprecations should be non-controversial, others a bit more.
>> If a deprecation is really controversial, it might warrant its own 
>> dedicated RFC or be dropped altogether.
>>
>>
>> Best regards,
>>
>> Gina P. Banyard
>
> Hello Internals,
>
> I added *Deprecate using “namespace” as a class constant or static 
> property name* to the RFC:
>
> https://wiki.php.net/rfc/deprecations_php_8_6#deprecate_using_namespace_as_a_class_constant_or_static_property_name 
>
>