-
Notifications
You must be signed in to change notification settings - Fork 7.9k
ext/xml: Deprecate xml_set_object() and passing non-callable strings to handlers #15293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
On mobile now, but looks like you missed updating some tests, I'll have a look once that's done. |
Erg, everything was passing locally |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation looks fine, only test + wording remarks
ext/xml/tests/xml_set_processing_instruction_handler_basic.phpt
Outdated
Show resolved
Hide resolved
…uld be triggered with other code looking at the bug report
99f0a31
to
d228e38
Compare
@Girgias I'm looking at the "Passing non-callable strings to the xml_set_*_handler() functions is now deprecated." part of the deprecation, in particular with respect to this: "This would also mean to unset a handler the value of null must be used instead of an empty string which is also currently allowed. " It looks like there are no tests passing an empty string for the handler. And a quick test run also doesn't show a deprecation notice for an empty string as a callback: https://3v4l.org/AdVej/rfc#vgit.master What am I missing ? |
It is producing a deprecation notice locally for me. I am guessing 3v4l.org hasn't pulled the latest master yet. |
@Girgias Thanks for clarifying and adding the test. And good point about the |
FYI: pinged 3v4l about the master branch being behind (in principle it should update daily, so something has probably broken) |
RFC: https://wiki.php.net/rfc/deprecations_php_8_4#xml_set_object_and_xml_set_handler_with_string_method_names