php-src/Zend/tests/bug71539_6.phpt

--TEST--
Bug #71539.5 (Memory error on $arr[$a] =& $arr[$b] if RHS rehashes)
--FILE--
<?php
$name = 'a';
for ($i = 0; $i < 100000; $i++) {
    if ($name != 'i') {
        $$name =& $GLOBALS;
    }
    $name++;
}
?>
OK
--EXPECT--
OK
Fixed bug #71539 (Memory error on $arr[$a] =& $arr[$b] if RHS rehashes) 2016-07-07 05:59:44 +08:00			`--TEST--`
			`Bug #71539.5 (Memory error on $arr[$a] =& $arr[$b] if RHS rehashes)`
			`--FILE--`
			`<?php`
			`$name = 'a';`
			`for ($i = 0; $i < 100000; $i++) {`
			`if ($name != 'i') {`
			`$$name =& $GLOBALS;`
			`}`
			`$name++;`
			`}`
			`?>`
			`OK`
			`--EXPECT--`
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 2018-10-15 10:33:09 +08:00			`OK`