diff options
| author | Peter Kokot <peterkokot@gmail.com> | 2018-10-14 12:54:08 +0200 |
|---|---|---|
| committer | Peter Kokot <peterkokot@gmail.com> | 2018-10-14 12:54:08 +0200 |
| commit | 60a69daec60f1886e166e8060556777819c66f98 (patch) | |
| tree | 728557dc23dcef2e95983fd272042912f5c1f712 /ext/zlib/tests/gzopen_include_path.inc | |
| parent | 6f343d29a5561c846b1c9d95af56ecb2d659166c (diff) | |
| download | php-git-60a69daec60f1886e166e8060556777819c66f98.tar.gz | |
Sync leading and final newlines in source code files
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
Diffstat (limited to 'ext/zlib/tests/gzopen_include_path.inc')
| -rw-r--r-- | ext/zlib/tests/gzopen_include_path.inc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ext/zlib/tests/gzopen_include_path.inc b/ext/zlib/tests/gzopen_include_path.inc index 7d6723a815..add04f74de 100644 --- a/ext/zlib/tests/gzopen_include_path.inc +++ b/ext/zlib/tests/gzopen_include_path.inc @@ -89,4 +89,4 @@ function teardown_relative_path() { rmdir($newdir); } } -?>
\ No newline at end of file +?> |