delta/php-git.git/ext/json, branch php-7.2.31 git.php.net: repository/php-src.git Fixed bug #77843 2019-04-23T10:43:07+00:00 Nikita Popov nikita.ppv@gmail.com 2019-04-23T10:43:07+00:00 4831e150c5ada631c1480098b8a42cbf024d8899 






Sync leading and final newlines in *.phpt sections
2018-10-15T02:31:31+00:00

Peter Kokot
peterkokot@gmail.com

2018-10-15T02:31:31+00:00

f1d7e3ca0b70f910fcecef0278de9c15440ca3c0

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





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 *.phpt
2018-10-14T17:44:14+00:00

Peter Kokot
peterkokot@gmail.com

2018-10-14T15:23:43+00:00

17ccbeec3242b80f84fbf6b3acd58421ef003b02












Sync leading and final newlines in source code files
2018-10-14T10:54:08+00:00

Peter Kokot
peterkokot@gmail.com

2018-10-14T10:54:08+00:00

60a69daec60f1886e166e8060556777819c66f98

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





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 files
2018-10-13T12:14:50+00:00

Peter Kokot
peterkokot@gmail.com

2018-10-13T12:14:50+00:00

902d39a3a79c6efe93c8879575fdd5a759cf03de












year++
2018-01-02T04:55:14+00:00

Xinchen Hui
laruence@gmail.com

2018-01-02T04:55:14+00:00

7a7ec01a4976e72971948a93ca9eafa5752a3f91












Merge branch 'PHP-7.1' into PHP-7.2
2017-12-30T17:41:45+00:00

Jakub Zelenka
bukka@php.net

2017-12-30T17:41:45+00:00

84aad458ca87beaa6748135cf8b0e2013c56c07c












Use seialize_precision instead of precision in all json tests
2017-12-30T17:34:01+00:00

Jakub Zelenka
bukka@php.net

2017-12-30T17:34:01+00:00

2fd0b994dd938e4bff8588323d378161388eb9ff












Fix bug #68567 (JSON_PARTIAL_OUTPUT_ON_ERROR can result in JSON with null key)
2017-10-15T18:36:15+00:00

Jakub Zelenka
bukka@php.net

2017-10-15T18:36:15+00:00

7c556c44a10bfc53c37295626e61bd99dc4f550c












Prevent from being affected by local php.ini
2017-10-13T10:23:56+00:00

Xinchen Hui
laruence@gmail.com

2017-10-13T10:23:56+00:00

21f049b45c6bdd7a65bafe74410f0dcbbb7f3b46