#
08a30628 |
| 08-Apr-2019 |
Nikita Popov |
Merge branch 'PHP-7.2' into PHP-7.3
|
#
d7b5954f |
| 08-Apr-2019 |
Nikita Popov |
Fixed bug #77853 |
#
e6f86fb1 |
| 07-Apr-2019 |
Peter Kokot |
Merge branch 'PHP-7.4' * PHP-7.4: Remove checks for locale.h, setlocale, localeconv
|
#
e06836a1 |
| 24-Feb-2019 |
Peter Kokot |
Remove checks for locale.h, setlocale, localeconv The `<loccale.h>` header file, setlocale, and localeconv are part of the standard C89 [1] and on current systems can be used uncondition
Remove checks for locale.h, setlocale, localeconv The `<loccale.h>` header file, setlocale, and localeconv are part of the standard C89 [1] and on current systems can be used unconditionally. Since PHP 7.4 requires at least C89 or greater, the `HAVE_LOCALE_H`, `HAVE_SETLOCALE`, and `HAVE_LOCALECONV` symbols defined by Autoconf in configure.ac [2] can be ommitted and simplifed. The bundled libmagic (file) has also been patched already in version 5.35 and up in upstream location so when it will be patched also in php-src the check for locale.h header is still left in the configure.ac and in windows headers definition file. [1] https://port70.net/~nsz/c/c89/c89-draft.html#4.4 [2] https://git.savannah.gnu.org/cgit/autoconf.git/tree/lib/autoconf/headers.m4 Omit the bundled libmagic files
show more ...
|
#
309edb07 |
| 07-Apr-2019 |
Peter Kokot |
Merge branch 'PHP-7.4' * PHP-7.4: Remove HAVE_LIMITS_H
|
#
fd1ad1e2 |
| 07-Apr-2019 |
Peter Kokot |
Remove HAVE_LIMITS_H The `<limits.h>` header file is part of the standard C89 headers [1] and on current systems can be included unconditionally. Since PHP requires at least C89
Remove HAVE_LIMITS_H The `<limits.h>` header file is part of the standard C89 headers [1] and on current systems can be included unconditionally. Since PHP requires at least C89 or greater, the `HAVE_LIMITS_H` symbol defined by Autoconf in configure.ac [2] can be ommitted and simplifed however due to bundled file library (libmagic) and timelib still using it, the removal there was omitted and done only in Zend.m4 file. Current bundled libraries libtime, oniguruma, and libmagic still include partial `HAVE_LIMITS_H` usage and will be more refactored when this is possible. Refs: [1] https://port70.net/~nsz/c/c89/c89-draft.html#4.1.2 [2] https://git.savannah.gnu.org/cgit/autoconf.git/tree/lib/autoconf/headers.m4
show more ...
|
#
ba2269ab |
| 30-Mar-2019 |
Anatol Belski |
Fix memory leak |
Revision tags: php-7.3.3RC1, php-7.2.16RC1 |
|
#
879cd049 |
| 18-Feb-2019 |
Nikita Popov |
Merge branch 'PHP-7.4'
|
#
9249d820 |
| 18-Feb-2019 |
Tyson Andre |
Fix typos in code comments [skip ci] |
#
bd13c209 |
| 14-Feb-2019 |
Nikita Popov |
Merge branch 'PHP-7.4'
|
#
96daef04 |
| 14-Feb-2019 |
Nikita Popov |
Make ABI of SIMD optimized functions independent of compiler flags Always export these as normal functions and only use function pointers internally if necessary. |
#
fdb85a82 |
| 11-Feb-2019 |
Nikita Popov |
Return empty str from quotemeta() on empty str |
Revision tags: php-7.2.15, php-7.3.2 |
|
#
623911f9 |
| 03-Feb-2019 |
Peter Kokot |
Merge branch 'PHP-7.4' * PHP-7.4: Remove local variables
|
Revision tags: php-7.2.15RC1 |
|
#
92ac598a |
| 22-Jan-2019 |
Peter Kokot |
Remove local variables This patch removes the so called local variables defined per file basis for certain editors to properly show tab width, and similar settings. These are mainly
Remove local variables This patch removes the so called local variables defined per file basis for certain editors to properly show tab width, and similar settings. These are mainly used by Vim and Emacs editors yet with recent changes the once working definitions don't work anymore in Vim without custom plugins or additional configuration. Neither are these settings synced across the PHP code base. A simpler and better approach is EditorConfig and fixing code using some code style fixing tools in the future instead. This patch also removes the so called modelines for Vim. Modelines allow Vim editor specifically to set some editor configuration such as syntax highlighting, indentation style and tab width to be set in the first line or the last 5 lines per file basis. Since the php test files have syntax highlighting already set in most editors properly and EditorConfig takes care of the indentation settings, this patch removes these as well for the Vim 6.0 and newer versions. With the removal of local variables for certain editors such as Emacs and Vim, the footer is also probably not needed anymore when creating extensions using ext_skel.php script. Additionally, Vim modelines for setting php syntax and some editor settings has been removed from some *.phpt files. All these are mostly not relevant for phpt files neither work properly in the middle of the file.
show more ...
|
#
0cf7de1c |
| 30-Jan-2019 |
Zeev Suraski |
Remove yearly range from copyright notice |
#
38c337f2 |
| 30-Jan-2019 |
Zeev Suraski |
Remove year range from copyright notice |
#
c97b9aa2 |
| 29-Jan-2019 |
Nikita Popov |
Always treat needles as strings This is part of https://wiki.php.net/rfc/deprecations_php_7_3. |
#
ff780fec |
| 28-Jan-2019 |
Nikita Popov |
Require second argument on (mb_)parse_str() This was deprecated in PHP 7.2 as part of https://wiki.php.net/rfc/deprecations_php_7_2. |
Revision tags: php-7.3.2RC1, php-5.6.40, php-7.1.26, php-7.3.1, php-7.2.14 |
|
#
b1e9c73b |
| 29-Dec-2018 |
Andreas Treichel |
Allow strip_tags with an array of allowed tagnames |
#
1bc86bcd |
| 18-Jan-2019 |
Nikita Popov |
Merge branch 'PHP-7.3'
|
#
986b9b5a |
| 18-Jan-2019 |
Nikita Popov |
Add additional no_sanitize_address attributes To fix bug #77447 in release mode as well. |
#
e219ec14 |
| 07-Jan-2019 |
Nikita Popov |
Implement typed properties RFC: https://wiki.php.net/rfc/typed_properties_v2 This is a squash of PR #3734, which is a squash of PR #3313. Co-authored-by: Bob Weinand <bobwe
Implement typed properties RFC: https://wiki.php.net/rfc/typed_properties_v2 This is a squash of PR #3734, which is a squash of PR #3313. Co-authored-by: Bob Weinand <bobwei9@hotmail.com> Co-authored-by: Joe Watkins <krakjoe@php.net> Co-authored-by: Dmitry Stogov <dmitry@zend.com>
show more ...
|
Revision tags: php-7.2.14RC1, php-7.3.1RC1, php-5.6.39, php-7.1.25, php-7.2.13, php-7.0.33 |
|
#
3b0f0511 |
| 02-Dec-2018 |
Christoph M. Becker |
Allow empty $escape to eschew escaping CSV Albeit CSV is still a widespread data exchange format, it has never been officially standardized. There exists, however, the “informational” R
Allow empty $escape to eschew escaping CSV Albeit CSV is still a widespread data exchange format, it has never been officially standardized. There exists, however, the “informational” RFC 4180[1] which has no notion of escape characters, but rather defines `escaped` as strings enclosed in double-quotes where contained double-quotes have to be doubled. While this concept is supported by PHP's implementation (`$enclosure`), the `$escape` sometimes interferes, so that `fgetcsv()` is unable to correctly parse externally generated CSV, and `fputcsv()` is sometimes generating non-compliant CSV. Since PHP's `$escape` concept is availble for many years, we cannot drop it for BC reasons (even though many consider it as bug). Instead we allow to pass an empty string as `$escape` parameter to the respective functions, which results in ignoring/omitting any escaping, and as such is more inline with RFC 4180. It is noteworthy that this is almost no userland BC break, since formerly most functions did not accept an empty string, and failed in this case. The only exception was `str_getcsv()` which did accept an empty string, and used a backslash as escape character then (which appears to be unintended behavior, anyway). The changed functions are `fputcsv()`, `fgetcsv()` and `str_getcsv()`, and also the `::setCsvControl()`, `::getCsvControl()`, `::fputcsv()`, and `::fgetcsv()` methods of `SplFileObject`. The implementation also changes the type of the escape parameter of the PHP_APIs `php_fgetcsv()` and `php_fputcsv()` from `char` to `int`, where `PHP_CSV_NO_ESCAPE` means to ignore/omit escaping. The parameter accepts the same values as `isalpha()` and friends, i.e. “the value of which shall be representable as an `unsigned char` or shall equal the value of the macro `EOF`. If the argument has any other value, the behavior is undefined.” This is a subtle BC break, since the character `chr(128)` has the value `-1` if `char` is signed, and so likely would be confused with `EOF` when converted to `int`. We consider this BC break to be acceptable, since it's rather unlikely that anybody uses `chr(128)` as escape character, and it easily can be fixed by casting all `escape` arguments to `unsigned char`. This patch implements the feature requests 38301[2] and 51496[3]. [1] <https://tools.ietf.org/html/rfc4180> [2] <https://bugs.php.net/bug.php?id=38301> [3] <https://bugs.php.net/bug.php?id=51496>
show more ...
|
Revision tags: php-7.3.0, php-7.1.25RC1, php-7.2.13RC1, php-7.3.0RC6, php-7.1.24, php-7.2.12, php-7.3.0RC5 |
|
#
9afce019 |
| 01-Nov-2018 |
Zeev Suraski |
Future-proof email addresses |
#
67e0138c |
| 01-Nov-2018 |
Zeev Suraski |
Future-proof email addresses... |