fix: libxml2 related deprecated issues in v3 - #3455
Merged
Merged
Conversation
|
theseion
approved these changes
Oct 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Similar as #3454 for v2.
what
This PR fixes libxml2 related deprecated warnings.
why
With newest
clangandgcccompilers and newestlibxml2library there were a few deprecated warnings.I removed not just
xmlThrDefSetGenericErrorFunc()call but thexmlSetGenericErrorFunc()too, because in libxml2 documentation both functions are marked as deprecated.Beside of that, all error handlers are set to a
null_error()function which did nothing, so I remove those handlers too, and set the contexts' options toXML_PARSE_NOWARNING | XML_PARSE_NOERRORas libxml2's documentation recommends that.references
"If you only want to disable parser errors being printed to stderr, use xmlParserOption
XML_PARSE_NOERROR"