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.

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

show more ...

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.

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

show more ...

Trim trailing whitespace in source code files

Trim trailing whitespace in source code files

year++

year++

Yet one /nologo

Add /nologo

Fix command

Fix `nmake install` fails when there are no shared extensions

check for existence instead of muting everything

check for exe existence before trying to copy

Fix .pgd name for ts build

cleanup discontinued target

parametrize zip names

simplify names

Pass explicit PHP version string to mkdist.php

Fix command syntax, env var has to be nmake macro in makefile

use php.exe from the SDK for packaging, not the one just compiled

Support run or test target invoked within debugger

Useful, as it gets all the environment produced by the makefile. For the
test target, it might make sense to have the child process deb

Support run or test target invoked within debugger

Useful, as it gets all the environment produced by the makefile. For the
test target, it might make sense to have the child process debug plugin
for VS installed.

show more ...

Update copyright headers to 2017

Update copyright headers to 2017

Update copyright headers to 2017

Use $(CC) consistently in the Makefile

add run target

With this it is possible to run some code with the currently compiled
PHP and all the required environment included.

rename the env setting target and reuse it for build-snap

fix test run with autogenerated ini

generate test ini file, so shared exts are loaded for nmake test