| #
dd8d8bf8 |
| 17-Oct-2018 |
Peter Kokot |
Sync final and leading newlines
This patch adds some missing newlines, trims some multiple redundant
final newlines into a single one, and trims few redundant leading
newlines.
Sync final and leading newlines
This patch adds some missing newlines, trims some multiple redundant
final newlines into a single one, and trims few 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
show more ...
|
| #
3cc94915 |
| 05-Dec-2012 |
Daniel P. Brown |
Change multiple checks and references from 'www.php.net' to plainly 'php.net' to reduce 301's, fix a few broken items, and ease a bit of the load off the server (multiple connections per page when st
Change multiple checks and references from 'www.php.net' to plainly 'php.net' to reduce 301's, fix a few broken items, and ease a bit of the load off the server (multiple connections per page when statically referenced as 'www.php.net.'
show more ...
|
