Re: RFC: CLI behave like SH or PERL/RUBY/PYTHON?
| From: | Yasuo Ohgaki | Date: | Wed, 23 Oct 2002 08:28:23 +0000 |
| Subject: | Re: RFC: CLI behave like SH or PERL/RUBY/PYTHON? | ||
| References: | 1 2 3 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-89970@lists.php.net to get a copy of this message | ||
Hartmut Holzgraefe wrote:
Edin Kadribasic wrote: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. -- Yasuo OhgakiDoing 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?