RE: [PHP-DEV] Re: [PHP-CVS] output handlers

can we please be careful with reply-to-all? i just got this mail 4 times. everyone on both php-cvs and php-dev got it 3 times. Thanks, James > -----Original Message----- > From: Zeev Suraski [mailto:zeev@zend.com] > Sent: Tuesday, August 06, 2002 2:49 PM > To: Yasuo Ohgaki > Cc: php-dev@lists.php.net; marcus.boerger@post.rwth-aachen.de; James > Cox; php-cvs@lists.php.net; php-dev@lists.php.net > Subject: Re: [PHP-DEV] Re: [PHP-CVS] output handlers > > > At 17:00 06/08/2002, Yasuo Ohgaki wrote: > >Zeev Suraski wrote: > >>I haven't noticed this discussion before, but I'm very much against > > > >Don't worry you haven't miss much. > > > >>removing or deprecating output_handler. If you want to write a > portable > >>app, you should indeed register output handlers in your app; But > >>generally speaking, output handlers are functions which are very likely > >>to be implemented on a site-wide basis, and not necessarily a > script- or > >>app-wide basis. For such purposes, php.ini is the right place. > > > >Ok. You are asking for trouble > >and some people criticize "PHP is endlessly > >configurable by php.ini" :( > > I'm very much against configuration options that affect the way the > language behaves; But supplying server-wide settings that allow you to > deploy your site in a certain way are a good thing in my opinion. They > should also be transparent to well-written applications. > > Why would an I18N app not work with output_handler? > > Zeev > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > >