delta/php-git.git/ext/gettext, branch php-7.2.31 git.php.net: repository/php-src.git 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












Fixed incorrect restoring of LDFLAGS
2018-08-05T18:26:40+00:00

sji
shinji.igarashi@gmail.com

2018-07-12T13:23:47+00:00

0f557756dd3bb7a6390894e04f9ca25333c88d67












year++
2018-01-02T04:53:31+00:00

Xinchen Hui
laruence@gmail.com

2018-01-02T04:53:31+00:00

ccd4716ec77c60391d63a1a6af72f96a09b1c617












Fixed bug #73730 (textdomain(null) throws in strict mode)
2017-09-10T16:39:29+00:00

Christoph M. Becker
cmbecker69@gmx.de

2017-09-10T16:39:29+00:00

4b746fce1c6f873a696ace4c98e0981a059f35c9

The $text_domain parameter may be NULL, which we have to cater to
explicitly with regard to strict_types.





The $text_domain parameter may be NULL, which we have to cater to
explicitly with regard to strict_types.







ext/gettext: respect passed in library directory for all checks
2017-04-17T07:11:40+00:00

Michael Heimpold
mhei@heimpold.de

2017-04-13T20:43:26+00:00

32c5b8efd68dd21dd025285e7207dcab7c6319cd

A directory given to configure by --with-gettext=dir is only
used within the very first AC_CHECK_LIB. This is because the
temporary modified LDFLAGS variable is reset too early.

This results in functions not detected properly.

The original issue and patch was reported for OpenWrt/LEDE
distribution by @Dimazhan at:
https://github.com/openwrt/packages/issues/4250

Signed-off-by: Michael Heimpold <mhei@heimpold.de>





A directory given to configure by --with-gettext=dir is only
used within the very first AC_CHECK_LIB. This is because the
temporary modified LDFLAGS variable is reset too early.

This results in functions not detected properly.

The original issue and patch was reported for OpenWrt/LEDE
distribution by @Dimazhan at:
https://github.com/openwrt/packages/issues/4250

Signed-off-by: Michael Heimpold <mhei@heimpold.de>







Update copyright headers to 2017
2017-01-04T17:14:55+00:00

Sammy Kaye Powers
sammyk@sammykmedia.com

2017-01-04T17:14:55+00:00

478f119ab9100dbd345a6db5287a0cfb5fda5bf3












Remove zpp fallback code (always use Fast ZPP)
2016-09-11T21:44:46+00:00

Andrea Faulds
ajf@ajf.me

2016-09-11T21:44:46+00:00

d690014bf35507ccb7a1150a27504d2f87848842

Squashed commit of the following:

commit 3e27fbb3d22b42d181e15c345f1c59a007b6b58c
Author: Andrea Faulds <ajf@ajf.me>
Date:   Sun Sep 11 19:14:37 2016 +0100

    Keep dummy FAST_ZPP macro for compatibility

commit 8a7cfd00deaa4a3c5026c97580c49c886c72a5b4
Author: Andrea Faulds <ajf@ajf.me>
Date:   Mon Sep 5 22:36:03 2016 +0100

    Remove FAST_ZPP macro and plain zpp fallback code





Squashed commit of the following:

commit 3e27fbb3d22b42d181e15c345f1c59a007b6b58c
Author: Andrea Faulds <ajf@ajf.me>
Date:   Sun Sep 11 19:14:37 2016 +0100

    Keep dummy FAST_ZPP macro for compatibility

commit 8a7cfd00deaa4a3c5026c97580c49c886c72a5b4
Author: Andrea Faulds <ajf@ajf.me>
Date:   Mon Sep 5 22:36:03 2016 +0100

    Remove FAST_ZPP macro and plain zpp fallback code