ext/Intl: Return PHP_INT_MIN as int from MessageFormatter::parse() on 64-bit#22131
Open
LamentXU123 wants to merge 2 commits into
Open
ext/Intl: Return PHP_INT_MIN as int from MessageFormatter::parse() on 64-bit#22131LamentXU123 wants to merge 2 commits into
LamentXU123 wants to merge 2 commits into
Conversation
devnexen
reviewed
May 22, 2026
devnexen
reviewed
May 22, 2026
Member
|
Anyhow, I ll look into it in your intl PRs in one swoop later. |
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.
Cleaning up.
-ZEND_LONG_MAXdoes not equals toZEND_LONG_MIN, because signed integer ranges are not symmetricin 64-bit
This makes -9,223,372,036,854,775,808 in MessageFormatter be degraded into float, but it could be an integer.
result in
But it should be
Reproduce
This is really a super super edge case. I don't even sure we should treat this as a bug fix or a refactor at this point. It really do come into my mind when I am looking at this code that I don't even think we need any NEWS or UPGRADING entry for this little fix. No similar bugs in the code base.