summaryrefslogtreecommitdiff
path: root/ext/intl
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* | | Improve fix for bug #76829Anatol Belski2018-09-011-7/+15
| | |
* | | Fixed bug #76829 Incorrect validation of domain on idn_to_utf8() functionAnatol Belski2018-09-012-2/+18
| | | | | | | | | | | | | | | | | | | | | As stated by RFC 5890, U-Labels might be up to 252 Unicode code points long. This can be fixed in 7.1+ as well, but there might potentially be issues in some existing apps expecting the output to be max 255 octets long. Thus it seems to be safer to not to touch stable branches.
* | | Merge branch 'PHP-7.2' into PHP-7.3Anatol Belski2018-08-092-0/+52
|\ \ \ | |/ / | | | | | | | | | * PHP-7.2: Fixed bug #74484 MessageFormatter::formatMessage memory corruption
| * | Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2018-08-092-0/+52
| |\ \ | | |/ | | | | | | | | | * PHP-7.1: Fixed bug #74484 MessageFormatter::formatMessage memory corruption
| | * Fixed bug #74484 MessageFormatter::formatMessage memory corruptionAnatol Belski2018-08-092-0/+52
| | | | | | | | | | | | with 11+ named placeholder
* | | Remove unused variablesGabriel Caruso2018-07-252-3/+1
| | |
* | | Remove unused Git attributes identPeter Kokot2018-07-2511-19/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The $Id$ keywords were used in Subversion where they can be substituted with filename, last revision number change, last changed date, and last user who changed it. In Git this functionality is different and can be done with Git attribute ident. These need to be defined manually for each file in the .gitattributes file and are afterwards replaced with 40-character hexadecimal blob object name which is based only on the particular file contents. This patch simplifies handling of $Id$ keywords by removing them since they are not used anymore.
* | | Give a reason why the test was skippedGabriel Caruso2018-07-223-6/+6
| | | | | | | | | | | | | | | | | | This will help us debug why a test was skipped in GCOV (http://gcov.php.net/viewer.php?version=PHP_HEAD&func=skip), and maybe put them to run again
* | | Fixed testsDmitry Stogov2018-07-121-10/+10
| | |
* | | Export stdClass objects using (object) cast (fixes #48016)Andrea Faulds2018-07-122-20/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | Before this change, var_export()'s output for stdClass objects calls the non-existent stdClass::__set_state method, and is therefore useless. This commit makes var_export() output an (object) cast from an array instead, which when evaluated, will produce a stdClass object. Other classes see unchanged output.
* | | Uze ZVAL_COPY_DEREF() instead of ZVAL_DEREF() and ZVAL_COPY()Dmitry Stogov2018-07-092-4/+2
| | |
* | | Use zval_ptr_dtor() instead of legacy zval_dtor(), to destroy unused values ↵Dmitry Stogov2018-07-051-4/+4
| | | | | | | | | | | | returned from PHP functions (they may be circular data structures).
* | | Replace zval_dtor() with specialized destructorsDmitry Stogov2018-07-051-2/+2
| | |
* | | Don't keep dangling pointer to function_nameDmitry Stogov2018-07-051-1/+2
| | |
* | | Use zval_ptr_dtor() instead of zval_dtor() in internal functions that ↵Dmitry Stogov2018-07-053-14/+14
| | | | | | | | | | | | destroy new created object (This is safer and produces less code)
* | | Fixed incorrrecr zval_dtor() usage to replace value of argument passed by ↵Dmitry Stogov2018-07-053-9/+7
| | | | | | | | | | | | reference, that may lead to memory leaks.
* | | Replace legacy zval_dtor() by zval_ptr_dtor_nogc() or even more specialized ↵Dmitry Stogov2018-07-046-14/+14
| | | | | | | | | | | | | | | | | | | | | destructors. zval_dtor() doesn't make a lot of sense in PHP-7.* and it's used incorrectly in some places. Its occurances should be replaced by zval_ptr_dtor() or zval_ptr_dtor_nogc(), or even more specialized destructors.
* | | Avoid magic method hash lookupsDmitry Stogov2018-07-022-3/+3
| | |
* | | Merge branch 'PHP-7.2'Christoph M. Becker2018-07-011-1/+1
|\ \ \ | |/ / | | | | | | | | | * PHP-7.2: Make newly introduced bug76556.phpt more resilient
| * | Merge branch 'PHP-7.1' into PHP-7.2Christoph M. Becker2018-07-011-1/+1
| |\ \ | | |/ | | | | | | | | | * PHP-7.1: Make newly introduced bug76556.phpt more resilient
| | * Make newly introduced bug76556.phpt more resilientChristoph M. Becker2018-07-011-1/+1
| | | | | | | | | | | | | | | Obviously, different compilers mangle the C++ class name differently. We should neither expect a prefix nor a suffix.
* | | Merge branch 'PHP-7.2'Christoph M. Becker2018-06-302-1/+24
|\ \ \ | |/ / | | | | | | | | | * PHP-7.2: Fix #76556: get_debug_info handler for BreakIterator shows wrong type
| * | Merge branch 'PHP-7.1' into PHP-7.2Christoph M. Becker2018-06-302-1/+24
| |\ \ | | |/ | | | | | | | | | * PHP-7.1: Fix #76556: get_debug_info handler for BreakIterator shows wrong type
| | * Fix #76556: get_debug_info handler for BreakIterator shows wrong typeChristoph M. Becker2018-06-302-1/+24
| | | | | | | | | | | | | | | | | | | | | We use the retrieved type for the "type" element instead of the text. This has been confused during the PHP 7 upgrade[1]. [1] http://git.php.net/?p=php-src.git;a=commit;h=1d793348067e5769144c0f7efd86428a4137baec
* | | Merge branch 'PHP-7.2'Anatol Belski2018-06-2512-5/+356
|\ \ \ | |/ / | | | | | | | | | * PHP-7.2: Prepare tests for ICU 62.1
| * | Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2018-06-2512-5/+356
| |\ \ | | |/ | | | | | | | | | * PHP-7.1: Prepare tests for ICU 62.1
View Lorry Controller Status