At 09:15 25/10/2002, Yasuo Ohgaki wrote:
Zeev Suraski wrote:
You print something, it doesn't print out. How is it trivial to solve
this? If you happen to know that there's IO buffering and that there's a
function called flush() then maybe it trivial, but then there are the
other million users who don't. Hence the idea of setting is to implicit
flush for the masses, who not only don't know about the existence of
flush(), but also don't know why it's even necessary.
Ok. If we are argue about what is mass or not
Don't forget about
- millions(?) of _current_ PHP users who are used to implicit_flush=off
by default.
Few of them use CLI.
- millions of decent programmers who are used to _usual_ behavior.
I consider myself a decent programmer, and I also consider the need to
flush explicitly extremely annoying. Moreover, many PHP programmers (if
not most) aren't used to this 'usual' behavior, because they either never
programmed in another language, or they still didn't bump into that
specific behavior.
- millions of scripts/echo/print don't need automatic flush at all.
i.e. much fewer number of script/echo/print need auto flushing.
It doesn't matter. When you're screwed by the lack of implicit flush, it's
much worse than a mere slow down.
Please list programming languages (i.e. not shell) that do
automatic/inefficient/unneeded flushing by default in program mode.
Read my fingertips - PHP IN CLI MODE. There's one, that's the only one I
care about.
If we are argue about difficulty of flushing,
We're not. We're arguing about the obscurity of the problem.
Zeev
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
