Ok. Let's agree that the current implementation is not ideal, but it works. There were already several suggestions on how this can be improved, but I don't think this is the right time to start doing it.
So my proposal is that Yasuo reverts his patch until 4.3.0 is branched and then let's have a look at how to solve CLI ini/flush issues. Edin On Wednesday 23 October 2002 10:28, Yasuo Ohgaki wrote: > Hartmut Holzgraefe wrote: > > Edin Kadribasic wrote: > >>Doing flush after each output operation does carry a performance penalty. > >> The following example illustrates it: > >> > >>php -d implicit_flush=0 -r 'for ($i=0; $i<1000000; $i++) echo $i;' > file > >> > >>This one executes about twice as fast on my machine compared to php with > >>implicit_flush turned on. The example is of course written to emphasise > >> the issue. > > > > ? default implicit_flush to isatty(stdout) should help here? > > This may be a great idea. > > There is cons also. Users may be looking the file > with tail... > > We are better to have ability enable/disable implicit flushing > at user's will. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
