Re: RFC: CLI behave like SH or PERL/RUBY/PYTHON?
| From: | Edin Kadribasic | Date: | Wed, 23 Oct 2002 07:41:05 +0000 |
| Subject: | Re: RFC: CLI behave like SH or PERL/RUBY/PYTHON? | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-89965@lists.php.net to get a copy of this message | ||
On Wednesday 23 October 2002 08:26, Yasuo Ohgaki wrote:
> I thought it's obvious choice, but it seems it's not.
>
> Which one you prefer CLI behave like
>
> SH
>
> or
>
> PERL/RUBY/PYTHON
It would perhaps be easier for us to understand if you explained what problem
you were trying to solve.
Here are some that I can see:
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.
OTOH, having implicit_flush turned on makes writing interactive command line
programs easier. Some programs (like pear installer) might even depend on it.
The way cli overwrites some ini settings is a whole different issue and I
don't thinks we should start mixing the two on this thread.
Edin