Introduce ReflectionProperty::getMangledName()

[mvorisek]

Description

repro: https://3v4l.org/2pnIb

Because the properties are renamed.

[iluuu1994]

This follows the normal mangling scheme for properties. Emitting a warning is not useful, because you can't really prevent it, and the code is not wrong. You need to change the way you access protected properties in an array created from an object to array cast.

[iluuu1994]

I'm assuming this is related to the suggestion in #18600 (comment). One thing that would be possible is providing something like ReflectionProperty::getMangledName(). Would that help? I agree that having to handle mangling yourself is not great.

[mvorisek]

ReflectionProperty::getMangledName() would be nice.

[nielsdos]

I agree. I retargeted the issue therefore to the introduction of such a method.

[mvorisek]

This issue is about renamed keys when casting array to object/stdClass. (3rd and 4th dump in [repro])

-> here I would not speak about any "mangling"

The ReflectionProperty::getMangledName() is about casting any object to array. (2nd dump in [repro])

-> here the result follow the property mangled names

[repro] https://3v4l.org/2pnIb

[iluuu1994]

There is no issue in your code. Property mangling is a feature that prevents naming collisions between properties with different visibilities. You need to use the mangled name when accessing values our of the properties hash table. This behavior is decades old (PHP 5.0).

[mvorisek]

(I have update my post above what I consider "mangling" and what not)