i think it's really quite simple.. be able to allow the developer the freedom to make their own mind up. As Harmut pointed out, some cli stuff needs implicit flushing. Other stuff doesn't -- i have many php scriptlets which do tasks for me that sh can't quite handle (or i don't know how to do it in sh).
just make it a per_script option (as has already been done, thank you Derick) and leave it alone. -- james > -----Original Message----- > From: Yasuo Ohgaki [mailto:yohgaki@;ohgaki.net] > Sent: Wednesday, October 23, 2002 2:44 PM > To: [EMAIL PROTECTED] > Subject: [PHP-DEV] The reason the way it is: About flushing... > Please read and comment. > > > This is obvious to me but it seems I have to explain... > > There are reasons why things are made in a certain way. > > shells, by its nature, it's interactive for the most > purposes, thus flushing every output make sense even > if it cost CPU time. > > programming languages, by its nature, most part of > programs do not have to be interactive even when > programmer is writing interactive programs. Thus, > flushing every output and lost CPU time does _not_ > make sense. > (I don't have to mention char device nature, right?) > > What we should do? > We make CLI a shell or programming language? > > Personally, I don't need PHP/CLI shell... > > Please speak up if you need PHP/CLI to be shell! > > -- > Yasuo Ohgaki > > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
