summaryrefslogtreecommitdiff
path: root/ext/zlib/tests/func.inc
diff options
context:
space:
mode:
authorPeter Kokot <peterkokot@gmail.com>2018-10-14 12:56:38 +0200
committerPeter Kokot <peterkokot@gmail.com>2018-10-14 12:56:38 +0200
commit1ad08256f349fa513157437abc4feb245cce03fc (patch)
treea6bd8d17fa64b625757ac04b1436696c3e760f61 /ext/zlib/tests/func.inc
parentf87f7bb8c7be413afd02548435112fa2c5030a4a (diff)
downloadphp-git-1ad08256f349fa513157437abc4feb245cce03fc.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/func.inc')
-rw-r--r--ext/zlib/tests/func.inc1
1 files changed, 0 insertions, 1 deletions
diff --git a/ext/zlib/tests/func.inc b/ext/zlib/tests/func.inc
index e431afedbf..7556f81e6a 100644
--- a/ext/zlib/tests/func.inc
+++ b/ext/zlib/tests/func.inc
@@ -16,4 +16,3 @@ function get_zlib_version()
return $version;
}
-