Re: [PHP-DEV] I hope this is the last email about this :) (was RFC:CLI behave like SH or PERL/RUBY/PYTHON?)
Derick Rethans wrote: On Wed, 23 Oct 2002, Yasuo Ohgaki wrote: Yes, since it should not set in php_cli.c. It's a lot confusing, bad thing to do with current code, inefficient, bad default, etc. It's a very good default Derick, It's a very _bad_ default. Fortunately, it's not released yet. That's why I'm against it strongly. IMO, flushing on every output by default is stupid setting. If you ever programmed interactive programs, you should know that unless you're ignorant about efficiency. I guess my questions are too hard to be understood by you compare to the last one. Derick, it seems you're alone so far. http://news.php.net/article.php?group=php.devarticle=89995 Do you finally realize your argument actually did not make sense? (Unless you need stupid PHP/CLI shell that requires start/end tag to do anything, of course ;) I'm going to fix it again unless many people want to make PHP/CLI behave like a shell rather than programming language. Alternatively, could you fix it again? (including Makefile.global) Thank you and I hope this is the last mail about this. PS: If you would like to write INI independent scripts, I suggest you to use php.ini-recommended at least. You don't/ didn't know phps crashing and make test does not work well with php.ini-recommended, nonetheless, you're insisting there is no problems. -- Yasuo Ohgaki -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] I hope this is the last email about this :) (was RFC:CLI behave like SH or PERL/RUBY/PYTHON?)
Edin Kadribasic wrote: I thought that we have agreed that you should revert the patch. You can now change the default behavior by both ini_set() and .the -d switch if you don't like the default. Yes. It's ok as a temporally solution, but not as a long term. I explicitly wrote I would like to see how it affects to Windows platform for few days and will modify the line afterwards. (Markus mentioned the setting may be needed for Windows) Anyway, it seems there is problems in ini handling code. If it's the case, we're better to fix everything now. http://news.php.net/article.php?group=php.devarticle=89995 This should explain the reason behind. Don't you think other language developers will make fun of the default auto flushing feature? If I were, I'll. The default is stupid and only Derick likes it, I suppose. ;) -- Yasuo Ohgaki Edin On Thursday 24 October 2002 00:27, Yasuo Ohgaki wrote: Derick Rethans wrote: On Wed, 23 Oct 2002, Yasuo Ohgaki wrote: Yes, since it should not set in php_cli.c. It's a lot confusing, bad thing to do with current code, inefficient, bad default, etc. It's a very good default Derick, It's a very _bad_ default. Fortunately, it's not released yet. That's why I'm against it strongly. IMO, flushing on every output by default is stupid setting. If you ever programmed interactive programs, you should know that unless you're ignorant about efficiency. I guess my questions are too hard to be understood by you compare to the last one. Derick, it seems you're alone so far. http://news.php.net/article.php?group=php.devarticle=89995 Do you finally realize your argument actually did not make sense? (Unless you need stupid PHP/CLI shell that requires start/end tag to do anything, of course ;) I'm going to fix it again unless many people want to make PHP/CLI behave like a shell rather than programming language. Alternatively, could you fix it again? (including Makefile.global) Thank you and I hope this is the last mail about this. PS: If you would like to write INI independent scripts, I suggest you to use php.ini-recommended at least. You don't/ didn't know phps crashing and make test does not work well with php.ini-recommended, nonetheless, you're insisting there is no problems. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] I hope this is the last email about this :) (was RFC:CLI behave like SH or PERL/RUBY/PYTHON?)
Im +1 for reverting the patch - (for what it's worth) Why? Well - most 'average' (and below) PHP programmers when attempting to do CLI programming, will get a serious WTF reaction from wondering why when they 'echo' stuff, it doesnt appear. The more advanced Users can manually turn off flushing, but for most small, quick scripts (eg. 50%+), this instant flush is going to be perfectly acceptable.. Anyway Just my 2c Regards Alan It's a very _bad_ default. Fortunately, it's not released yet. That's why I'm against it strongly. IMO, flushing on every output by default is stupid setting. If you ever programmed interactive programs, you should know that unless you're ignorant about efficiency. I guess my questions are too hard to be understood by you compare to the last one. Derick, it seems you're alone so far. http://news.php.net/article.php?group=php.devarticle=89995 Do you finally realize your argument actually did not make sense? (Unless you need stupid PHP/CLI shell that requires start/end tag to do anything, of course ;) I'm going to fix it again unless many people want to make PHP/CLI behave like a shell rather than programming language. Alternatively, could you fix it again? (including Makefile.global) Thank you and I hope this is the last mail about this. PS: If you would like to write INI independent scripts, I suggest you to use php.ini-recommended at least. You don't/ didn't know phps crashing and make test does not work well with php.ini-recommended, nonetheless, you're insisting there is no problems. -- Yasuo Ohgaki -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
