Skip to content

Workarounds for DOMDocument->xinclude() return #237

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

Merged
merged 7 commits into from
Mar 13, 2025
Merged

Conversation

alfsb
Copy link
Member

@alfsb alfsb commented Mar 9, 2025

DOMDocument->xinclude() returns negative numbers on partial executions, meaning that this return cannot be used for counting or stopping conditions on loops.

The old code sometimes reports errors of previous runs, also fixed.

The function xinclude_debug_report() can probably be removed, as the new warning reporting on failed XInclude now duplicated the errors, and is less expressive.

alfsb and others added 6 commits March 10, 2025 11:14
Co-authored-by: Kamil Tekiela <[email protected]>
Co-authored-by: Kamil Tekiela <[email protected]>
Co-authored-by: Kamil Tekiela <[email protected]>
Co-authored-by: Kamil Tekiela <[email protected]>
Co-authored-by: Kamil Tekiela <[email protected]>
Co-authored-by: Kamil Tekiela <[email protected]>
@alfsb alfsb merged commit 45f488c into php:master Mar 13, 2025
12 checks passed
@alfsb alfsb deleted the qax11 branch March 13, 2025 19:18
@alfsb
Copy link
Member Author

alfsb commented Mar 13, 2025

This fixed various real XInclude warnings, in almost all translations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants