[Sync-En] ext/intl: correct the offset semantics of localtime, parse and parseToCalendar - #3465
Merged
Conversation
…and parseToCalendar Translation of php/doc-en#4820 (commit 8871302): on return offset holds the position where parsing ended, whether or not it succeeded, and an out-of-range offset makes parsing fail immediately while leaving offset untouched. The localtime return value is described in full. EN-Revision updated.
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
1 participant
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.
Translation of php/doc-en#4820 (commit 8871302): on return
offsetholds the position where parsing ended, whether or not it succeeded, and an out-of-rangeoffsetmakes parsing fail immediately while leaving it untouched. The previous mention of-1is gone, and thelocaltime()return value is described in full. EN-Revision updated.Fixes: #3454