Re: cvs: php4 /tests/func 008.phpt 009.phpt

You do not test implicit flush here. You only ensure by testing that implicit_flush has no impact on some internal functions. One of Yasuos commit you removed was intended to ensure that buffering cannot be skipped in anyway when such internal functions are used. From my point of view Yasuos commit is not a real solution since it uses two more functions. In my outstanding patch mentioned already i am addressing this issue by adding new functions call php_ob_capture_start()/stop() and a better handling of the variables affecting buffering actions. marcus At 12:43 03.10.2002, Derick Rethans wrote:

derick          Thu Oct  3 06:43:44 2002 EDT

Added files:

    /php4/tests/func    008.phpt 009.phpt

Log: - Add tests Index: php4/tests/func/008.phpt +++ php4/tests/func/008.phpt --TEST-- Output buffering tests / Implicit flush off --POST-- --GET-- --INI-- implicit_flush=0 --FILE-- <?php $res = var_export("foo1"); echo "\n"; $res = var_export("foo2", TRUE); echo "\n"; echo $res."\n"; ?> --EXPECT-- 'foo1' 'foo2' Index: php4/tests/func/009.phpt +++ php4/tests/func/009.phpt --TEST-- Output buffering tests / Implicit flush off --POST-- --GET-- --INI-- implicit_flush=1 --FILE-- <?php $res = var_export("foo1"); echo "\n"; $res = var_export("foo2", TRUE); echo "\n"; echo $res."\n"; ?> --EXPECT-- 'foo1' 'foo2' -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php