Drop use of E_STRICT #391
Merged
Drop use of E_STRICT #391
Conversation
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
mentalstring
force-pushed
the
drop-E_STRICT
branch
from
7079e6e to
6afbac1
Compare
thePanz
reviewed
Nov 26, 2025
thePanz
approved these changes
Nov 26, 2025
mentalstring
force-pushed
the
drop-E_STRICT
branch
from
6afbac1 to
b20cb86
Compare
alquerci
approved these changes
Nov 29, 2025
thePanz
approved these changes
Nov 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This drop all uses of E_STRICT. Use of E_STRICT has been deprecated in PHP 8.4 and will be dropped in PHP 9.0. Since this project now requires PHP 7.4 and the use of E_STRICT has been mostly obsolete since then, this enables compatibility going forward.