Fix var name

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 ...

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 ...

Backport changes for OpenSSL 1.1.1 CI integration

Add debug message for failing test parts

(cherry picked from commit a45169a6ba54b13484d70cb474679c96347f779b)

Show all unm

Backport changes for OpenSSL 1.1.1 CI integration

Add debug message for failing test parts

(cherry picked from commit a45169a6ba54b13484d70cb474679c96347f779b)

Show all unmatched errors when test failed

(cherry picked from commit 70159652541c62b5f3bbb26da76b7e56987b2544)

More possibly colliding libs to remove from the test image

(cherry picked from commit 3008ad1a49210e4604522a987cbdd27a5a0a2c42)

Remove colliding file from CI image

(cherry picked from commit 6220d21c3420ff0d7366d410920ba5279fba3893)

Fix typo

(cherry picked from commit 24517d82cf8dc708d08bc77435ad418de4bdff4e)

show more ...

Switch to staging series on AppVeyor

Use stable deps on AppVeyor for now

as long as the latest image is not synced with VC++ 15.8

Do one test build with AVX

Don't prevent loading odbc and pdo_odbc for tests

One more folder to delete in AppVeyor image

remove another cygwin instance in AppVeyor run

Exclude ext/ftp from AppVeyor test run

as the tests depend on fork() and otherwise an extra setup would be
needed anyway.

Guard against AppVeyor losing deps issue

Possibly due to concurrent build cache updates or some changes in
the remote image. Some locking mechanism still could be required.

Next round on AppVeyor reliability.

enable ext/dba on AppVeyor

don't backup older deps after upgrades

always use staging deps for CI, that's what we have a CI for as well

parametrize crt, so only one place has to be changed

adjust deps dir naming scheme

not principal, just to have it same way as everywhere

switch AppVeyor to vc15 for master

update sdk version for appveyor and set explicit crt

Use zend_test shared for tests

The snapshot build enables everything it could find. The test run will
load all the shared exts as well, until defined otherwise. So no needs
for an ex

Use zend_test shared for tests

The snapshot build enables everything it could find. The test run will
load all the shared exts as well, until defined otherwise. So no needs
for an extra action.

show more ...

zend-test extension to house code that is required for testing internal APIs, but that we would not want to expose for regular builds

don't use separate deps for release branches

quick fix for the base branch version parsing, not perfect still