summaryrefslogtreecommitdiff
path: root/ext/intl
Commit message (Collapse)AuthorAgeFilesLines
* Relax test expectationChristoph M. Becker2020-02-031-2/+2
| | | | | | | Since we're dealing with floating point numbers, precision issues may hit us, and actually it's not necessary to check for the exact number anyway, because it is not exact in the first place. Therefore, we relax the test expectations.
* Fix #79212: NumberFormatter::format() may detect wrong typeChristoph M. Becker2020-02-032-15/+33
| | | | | | | | | | | We have to convert to number *before* detecting the type, to cater to internal objects implementing `cast_object`. We also get rid of the fallback behavior of using `FORMAT_TYPE_INT32`, because that can no longer happen; after `convert_scalar_to_number_ex` the type is either `IS_LONG` or `IS_DOUBLE`. We cater explicitly to the `IS_ARRAY` case what also avoids triggering a type confusion when `::TYPE_INT64` is passed as `$type`.
* Merge branch 'PHP-7.2' into PHP-7.3Stanislav Malyshev2019-11-112-2/+15
|\ | | | | | | | | * PHP-7.2: Fix bug #78804 - Segmentation fault in Locale::filterMatches
| * Fix bug #78804 - Segmentation fault in Locale::filterMatchesStanislav Malyshev2019-11-112-2/+15
| |
* | Merge branch 'PHP-7.2' into PHP-7.3Christoph M. Becker2019-10-044-0/+1559
|\ \ | |/ | | | | | | * PHP-7.2: Split intl tests for ICU 65
| * Split intl tests for ICU 65Christoph M. Becker2019-10-044-0/+1559
| |
* | Merge branch 'PHP-7.2' into PHP-7.3Nikita Popov2019-09-251-3/+3
|\ \ | |/
| * Fix hash key length in umsg_parse_format()Jinesh Patel2019-09-251-3/+3
| | | | | | | | | | Fix array length passed to zend_hash_str_find_ptr() casting from UChar array to char array requires mul by sizeof(UChar).
* | Merge branch 'PHP-7.2' into PHP-7.3Remi Collet2019-09-101-2/+2
|\ \ | |/ | | | | | | * PHP-7.2: Raise minimal GCC version, Test with 4.8 is OK With 4.4: error: #pragma GCC diagnostic not allowed inside functions
| * Raise minimal GCC version,Remi Collet2019-09-101-2/+2
| | | | | | | | | | Test with 4.8 is OK With 4.4: error: #pragma GCC diagnostic not allowed inside functions
* | Merge branch 'PHP-7.2' into PHP-7.3Christoph M. Becker2019-08-231-2/+7
|\ \ | |/ | | | | | | * PHP-7.2: Suppress deprecation warning on IDNA2003 ICU methods for clang
| * Suppress deprecation warning on IDNA2003 ICU methods for clangChristoph M. Becker2019-08-231-2/+7
| |
* | Merge branch 'PHP-7.2' into PHP-7.3Sara Golemon2019-08-161-0/+7
|\ \ | |/ | | | | | | * PHP-7.2: Suppress deprecation warning on IDNA2003 ICU methods
| * Suppress deprecation warning on IDNA2003 ICU methodsSara Golemon2019-08-161-0/+7
| |
* | Revert "Move to non deprecated API on suitable ICU versions"Sara Golemon2019-08-161-19/+1
| | | | | | | | | | | | This reverts commit 13a2f2d041999dca0066542f2a552798fab9a13d. The APIs used by this commit aren't entirely equivalent to the original ones.
* | Fix expect sectionAnatol Belski2019-06-011-1/+1
| |
* | Merge branch 'PHP-7.2' into PHP-7.3Anatol Belski2019-06-018-7/+377
|\ \ | |/ | | | | | | | | * PHP-7.2: Change ZPP only if compiled with ICU >= 64 Update tests for ICU 64
| * Change ZPP only if compiled with ICU >= 64Anatol Belski2019-06-011-1/+7
| |
| * Update tests for ICU 64Nikita Popov2019-06-018-7/+371
| | | | | | | | (cherry picked from commit 8a8bc5c4529223ecf4f421b1bed03618f7394335)
| * Convert CRLF to LFPeter Kokot2019-05-131-1/+1
| | | | | | | | | | These files are tracked with CRLF line endings in Git and can be converted to LF. Neither are parts of tests or code itself.
* | Merge branch 'PHP-7.2' into PHP-7.3Nikita Popov2019-04-152-1/+14
|\ \ | |/
| * Fixed bug #77895Nikita Popov2019-04-152-1/+14
| |
* | Merge branch 'PHP-7.2' into PHP-7.3Nikita Popov2019-03-181-3/+3
|\ \ | |/
| * Make test independent of icu versionNikita Popov2019-03-181-3/+3
| | | | | | | | | | We don't really care about the actual output here, just that it doesn't fail.
* | Merge branch 'PHP-7.2' into PHP-7.3Nikita Popov2019-03-182-1/+13
|\ \ | |/
| * Allow DateTimeImmutable in datefmt_format_object()Nikita Popov2019-03-182-1/+13
| | | | | | | | As pointed out in a comment on bug #65683.
* | Merge branch 'PHP-7.2' into PHP-7.3Anatol Belski2018-10-202-12/+12
|\ \ | |/ | | | | | | * PHP-7.2: Fix tests for ICU 63.1
| * Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2018-10-202-12/+12
| |\ | | | | | | | | | | | | * PHP-7.1: Fix tests for ICU 63.1
| | * Fix tests for ICU 63.1Anatol Belski2018-10-202-12/+12
| | | | | | | | | | | | The most of change is U+00A0 vs. new U+202F used in some outputs.
| | * Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-15162-252/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| | * Trim trailing whitespace in *.phptPeter Kokot2018-10-1467-175/+175
| | |
| | * Sync leading and final newlines in source code filesPeter Kokot2018-10-1415-17/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| | * Trim trailing whitespace in source code filesPeter Kokot2018-10-1311-161/+161
| | |
| | * Convert CRLF line endings to LFPeter Kokot2018-10-1312-137/+137
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch simplifies line endings tracked in the Git repository and syncs them to all include the LF style instead of the CRLF files. Newline characters: - LF (\n) (*nix and Mac) - CRLF (\r\n) (Windows) - CR (\r) (old Mac, obsolete) To see which line endings are in the index and in the working copy the following command can be used: `git ls-files --eol` Git additionally provides `.gitattributes` file to specify if some files need to have specific line endings on all platforms (either CRLF or LF). Changed files shouldn't cause issues on modern Windows platforms because also Git can do output conversion is core.autocrlf=true is set on Windows and use CRLF newlines in all files in the working tree. Unless CRLF files are tracked specifically, Git by default tracks all files in the index using LF newlines.
| | * Add test for bug #76942Anatol Belski2018-10-051-0/+33
| | |
| * | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-15162-252/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| * | Trim trailing whitespace in *.phptPeter Kokot2018-10-1467-175/+175
| | |
| * | Sync leading and final newlines in source code filesPeter Kokot2018-10-1415-17/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| * | Trim trailing whitespace in source code filesPeter Kokot2018-10-1311-161/+161
| | |
| * | Convert CRLF line endings to LFPeter Kokot2018-10-131-32/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch simplifies line endings tracked in the Git repository and syncs them to all include the LF style instead of the CRLF files. Newline characters: - LF (\n) (*nix and Mac) - CRLF (\r\n) (Windows) - CR (\r) (old Mac, obsolete) To see which line endings are in the index and in the working copy the following command can be used: `git ls-files --eol` Git additionally provides `.gitattributes` file to specify if some files need to have specific line endings on all platforms (either CRLF or LF). Changed files shouldn't cause issues on modern Windows platforms because also Git can do output conversion is core.autocrlf=true is set on Windows and use CRLF newlines in all files in the working tree. Unless CRLF files are tracked specifically, Git by default tracks all files in the index using LF newlines.
* | | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-15163-253/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Trim trailing whitespace in *.phptPeter Kokot2018-10-1469-185/+185
| | |
* | | Sync leading and final newlines in source code filesPeter Kokot2018-10-1412-12/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Trim trailing whitespace in source code filesPeter Kokot2018-10-133-6/+6
| | |
* | | Convert CRLF line endings to LFPeter Kokot2018-10-131-32/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch simplifies line endings tracked in the Git repository and syncs them to all include the LF style instead of the CRLF files. Newline characters: - LF (\n) (*nix and Mac) - CRLF (\r\n) (Windows) - CR (\r) (old Mac, obsolete) To see which line endings are in the index and in the working copy the following command can be used: `git ls-files --eol` Git additionally provides `.gitattributes` file to specify if some files need to have specific line endings on all platforms (either CRLF or LF). Changed files shouldn't cause issues on modern Windows platforms because also Git can do output conversion is core.autocrlf=true is set on Windows and use CRLF newlines in all files in the working tree. Unless CRLF files are tracked specifically, Git by default tracks all files in the index using LF newlines.
* | | Merge branch 'PHP-7.2' into PHP-7.3Anatol Belski2018-10-053-0/+38
|\ \ \ | |/ / | | | | | | | | | | | | * PHP-7.2: Add test for bug #76942 Fixed Bug #76942 U_ARGUMENT_TYPE_MISMATCH
| * | Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2018-10-053-0/+38
| |\ \ | | | | | | | | | | | | | | | | | | | | * PHP-7.1: Add test for bug #76942 Fixed Bug #76942 U_ARGUMENT_TYPE_MISMATCH
| | * | Add test for bug #76942Anatol Belski2018-10-051-0/+33
| | |/
| | * Fixed Bug #76942 U_ARGUMENT_TYPE_MISMATCHAnatol Belski2018-10-052-0/+5
| | | | | | | | | | | | ref bug #74484
* | | Remove invalid freeNikita Popov2018-09-181-1/+0
| | | | | | | | | | | | | | | The initialization of buffer has been moved further down in 7.3, so this free is no longer legal.
View Lorry Controller Status