Skip to content

Conversation

@mvorisek
Copy link
Contributor

@mvorisek mvorisek commented Nov 22, 2025

improve #19273

The method is extensively used [1], even small improvement of the deprecation warning is helpful to better understand why it is not needed anymore and since what version.

[1] used almost in every larger project/package

@mvorisek mvorisek changed the title Mention since in ReflectionXxx::setAccessible() method deprecation Add "since version" to ReflectionXxx::setAccessible() method deprecation Nov 22, 2025
@mvorisek mvorisek changed the title Add "since version" to ReflectionXxx::setAccessible() method deprecation Add "since version" to ReflectionXxx::setAccessible() method deprecation warning Nov 22, 2025
Copy link
Member

@DanielEScherzer DanielEScherzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wearing my ext/reflection maintainer hat: makes total sense
Wearing my 8.5 RM hat

  • I think this is okay to change, but please wait for @edorian to also approve this
  • For the various no-op closing functions that I implemented the deprecation for, I included the version the function became a no-op, but for finfo_close() which I didn't implement the message doesn't include the version. Do you want to add it there too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants