Use EXPECT instead of EXPECTF when possible

echo "Done\n";
?>
?>
Fatal error: Uncaught ArgumentCountError: explode() expects at least 2 parameters, 0 given in [no active file]:0
$triggerNotice+

Use EXPECT instead of EXPECTF when possible

echo "Done\n";
?>
?>
Fatal error: Uncaught ArgumentCountError: explode() expects at least 2 parameters, 0 given in [no active file]:0
$triggerNotice++;
?>
throw new Exception();
?>
?>
?>
?>
-- Testing date_parse() function with unexpected characters in $date argument --
?>
?>
-- Testing mktime() function with Zero arguments --
?>
?>
?>
echo "Done\n";
?>
echo "Done\n";
?>
echo "Done\n";
?>
?>
?>
?>
Arg value is: this is a string
?>
echo "Done";
?>
-- Testing posix_getgrgid() function with a negative group id --
echo "Done";
?>
-- Testing posix_getpgid() with negative pid --
echo "Done";
?>
-- Testing posix_getpwuid() function negative uid --
?>
echo "Done";
?>
-- Testing posix_kill() function with invalid signal --
echo "Done";
?>
-- Testing posix_strerror() function with invalid error number --
?>
-- Testing ReflectionMethod::getClosure() function with invalid object --
?>
?>
?>
-- Iteration 1 --
?>
?>
?>
echo "Done\n";
?>
echo"Done";
?>
echo "Done\n";
?>
echo "Done";
?>
-- Testing array_diff_assoc() function with zero arguments --
echo "Done";
?>
-- Testing array_diff() function with zero arguments --
-- Testing array_diff_key() function with less than expected no. of arguments --
?>
echo "Done"
?>
echo "Done";
?>
-- Iteration 1 --
echo "Done";
?>
-- Testing array_map() function with one less than expected no. of arguments --
echo "Done\n";
?>
--- Iteration 0 ---
echo"\nDone";
?>
?>
*** Variation with first two Arguments ***
echo "Done\n";
?>
echo "Done\n";
?>
echo "Done";
?>
echo "Done\n";
?>
echo "Done";
?>
echo "Done"
?>
?>
-- Testing usort() with built-in 'cmp_function': strcasecmp() --
echo "Done\n";
?>
echo "Done\n";
?>
echo "Done\n";
?>
--Iteration 1--
-- iteration 1 --
echo "Done\n";
echo "Done\n";
?>
*** Testing is_executable() on invalid files ***
echo "Done\n";
?>
echo "Done\n";
?>
*** Testing is_readable() on miscellaneous filenames ***
?>
echo "Done\n";
?>
*** Testing is_writable() with invalid filenames ***
?>
?>
echo "Done\n";
?>
?>
echo "Done\n";
?>
echo "Done\n";
?>
?>
?>
?>
?>
?>
?>
?>
-- Testing php_uname() function with invalid mode --
echo "Done\n";
?>
-- Iteration 1 --
echo "Done\n";
?>
-- Iteration 1 --
echo "Done\n";
?>

?>
*** Output for integer values ***
?>
lcg_value tests...
echo "Done\n";
?>
echo "Done\n";
?>
?>
echo "Done";
?>
-- Testing stream_set_timeout() function with a closed socket --
?>
-- Testing chr() function with no arguments --
echo "Done\n";
?>
echo "Done\n";
?>
echo "Done\n"
?>
?>
*** Using heredoc string ***
echo "Done\n";
?>
?>
Basic test WITH undefined var for result arg
?>
Test string with array values and results array
?>
-- Testing printf() function with Zero arguments --
echo "Done\n";
?>
echo "Done\n";
?>
echo "Done";
?>
-- Iteration 1 --
-- Testing sscanf() function with more than expected no. of arguments --
echo "Done\n";
?>
echo "*** Done ***";
?>
echo "*** Done ***";
?>
?>
-- Testing strval() function with object which has not toString() method --
?>
-- Variations for two arguments --
echo "\nDone";
?>
?>
?>
-- Testing strptime() function on failure --
echo "Done\n";
?>

show more ...

Clean DONE tags from tests

Remove most of the `===DONE===` tags and its variations.
Keep `===DONE===` if the test output otherwise becomes empty.

Closes GH-4872.

Replace dirname(__FILE__) by __DIR__ in tests

Adjust tests for zpp TypeError change

Sync leading and final newlines in *.phpt sections

This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in al

Sync leading and final newlines in *.phpt sections

This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in all
*.phpt sections.

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 *.phpt sections

This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in al

Sync leading and final newlines in *.phpt sections

This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in all
*.phpt sections.

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 *.phpt sections

This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in al

Sync leading and final newlines in *.phpt sections

This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in all
*.phpt sections.

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 *.phpt sections

This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in al

Sync leading and final newlines in *.phpt sections

This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in all
*.phpt sections.

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

Use int instead of integer in type errors

PHP requires integer typehints to be written "int" and does not
allow "integer" as an alias. This changes type error messages to
match the a

Use int instead of integer in type errors

PHP requires integer typehints to be written "int" and does not
allow "integer" as an alias. This changes type error messages to
match the actual type name and avoids confusing messages like
"must be of the type integer, integer given".

show more ...

Use "float" and "integer" in typehint and zpp errors

This commit was manufactured by cvs2svn to create branch 'PHP_5_3'.