Re: Re: cvs: php4 /main output.c

You are the one used unexported php_ob_* function in var.c :) I'll fix var.c, then. -- Yasuo Ohgaki Derick Rethans wrote:

On Thu, 3 Oct 2002, Yasuo Ohgaki wrote:

A little history. When 4.1.0 (or 4.2.0?) is released, I've fixed crush with deleting wrong buffer with implicit flush. The fix disabled implicit flush. I finally fixed implicit flush. Users should worry about implicit flush directive in php.ini now. e.g. implicit_flush=Off for normal use. Apparently, CLI SAPI implicitly enable implicit flush at initialization no matter what the php.ini setting is. CLI behavior is wrong, since there is no way to change implicit flush directive once script is started. I notified this to Edin and he would address this issue soon hopefully.

Can be, but implicit_flush is documented like this (which is correct): implicit_flush boolean FALSE by default. Changing this to TRUE tells PHP to tell the output layer to flush itself automatically after every output block. This is equivalent to calling the PHP function flush() after each and every call to print() or echo() and each and every HTML block. It says totally NOTHING about output buffering issues. This change also breaks internal functions: <?php $str = var_export ("foo", TRUE); ?> 'foo' (While it should not have dumped the contents at all). Please revert this, as this breaks backward compability BIG time, and IMO this is not a shortcoming of CLI. BTW, where did you get that implicit_flush should disable all output buffers? Derick -- ---------------------------------------------------------------------------

 Derick Rethans                                   http://derickrethans.nl/  JDI Media Solutions

--------------[ if you hold a unix shell to your ear, do you hear the c? ]-