Re: Re: output handlers

Yasuo Ohgaki wrote:

It's inconvenient/convenient like magic_qoute_gpc. If output handler is commonly used, programmers have to check if incompatible handler is registered in php.ini or not. Otherwise it may be end up with meaningless output/error. (For example, iconv handler should not be used with mbstring handler. The same applies to input handler...) Marcus and my idea is detecting wrong usage of output handlers. However, it's not only bug prone, but also the resolution introduces new issues as described. The best approch is not using the output_handler directive in php.ini. Any objection for discouraging output_handler usage?

Here is draft for new description. ========== start ============ ; You can redirect all of the output of your scripts to a function. For ; example, if you set output_handler to "mb_output_handler", charactor ; encoding will be transparently converted specified encoding. ; Setting an output handler automatically turns on output buffering. ; NOTE: People who wrote portable scripts should not depend on this ini ; directive. Set output handler by ob_start(). Using this ini ; directive may cause problems unless you know what script is doing. output_handler = =========== end ============== Any comments? -- Yasuo Ohgaki